lua/testes/locals.lua, branch v5.4.9 A mirror of https://github.com/lua/lua https://git.lua4.win/lua/atom?h=v5.4.9 2022-12-28T21:34:11+00:00 Avoid excessive name pollution in test files 2022-12-28T21:34:11+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2022-12-28T21:34:11+00:00 urn:sha1:314745ed8438d1276c6c928d5f9d4be018dfadb6 Test files are more polite regarding the use of globals when locals would do, and when globals are necessary deleting them after use. Bug: 'break' may not properly close variable in a 'for' loop 2022-08-24T20:36:47+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2022-08-24T20:36:47+00:00 urn:sha1:997f11f54322883c3181225f29d101a597f31730 Function 'leaveblock' was generating "break" label before removing variables from the closing block. If 'createlabel' created a 'close' instruction (which it did when matching a goto/break that exited the scope of an upvalue), that instruction would use the wrong level. Bug: 'lua_settop' may use an invalid pointer to stack 2022-05-25T20:41:39+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2022-05-25T20:41:39+00:00 urn:sha1:196bb94d66e727e0aec053a0276c3ad701500762 Bug: 'local function' can assign to '<const>' variables 2021-06-20T18:36:36+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-06-20T18:36:36+00:00 urn:sha1:6a0dace25a4b5b77f0fa6911de2ba26ef0fdff2c Bug: yielding in '__close' mess up number of returns 2021-04-16T18:41:44+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-04-16T18:41:44+00:00 urn:sha1:681297187ec45268e872b26753c441586c12bdd8 Yielding in a __close metamethod called when returning vararg results changes the top and so messes up the number of returned values. Bug: tbc variables in "for" loops don't avoid tail calls 2021-04-07T17:59:26+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-04-07T17:59:26+00:00 urn:sha1:47cffdc723c2e0c6dfaf62b7775ca1c1d338c0a4 New test module 'tracegc' 2021-03-01T16:54:29+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-03-01T16:54:29+00:00 urn:sha1:5276973224066e591b0f1a79c3b091d395848ac4 New module easies the inclusion of GC tracing in individual test files. '__close' methods can yield in the return of a C function 2021-02-12T16:36:30+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-02-12T16:36:30+00:00 urn:sha1:bc970005ce2e258e29a5c315ea4e49f76a66586e When, inside a coroutine, a C function with to-be-closed slots return, the corresponding metamethods can yield. ('__close' metamethods called through 'lua_closeslot' still cannot yield, as there is no continuation to go when resuming.) New implementation for to-be-closed variables 2021-02-09T17:00:05+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-02-09T17:00:05+00:00 urn:sha1:4e47f81188d37e29027158b76271d02a781242e2 To-be-closed variables are linked in their own list, embedded into the stack elements. (Due to alignment, this information does not change the size of the stack elements in most architectures.) This new list does not produce garbage and avoids memory errors when creating tbc variables. Correct order of return hooks vs. close metamethods 2021-01-21T13:27:22+00:00 Roberto Ierusalimschy roberto@inf.puc-rio.br 2021-01-21T13:27:22+00:00 urn:sha1:0e9254dfa03d95c3aa2888cf78e9a30bc88d41bc The return hook should be called only after closing variables (which are still part of the function). C functions were calling the hook before the metamethods.