lua, branch v5.5.1A mirror of https://github.com/lua/lua
https://git.lua4.win/lua/atom?h=v5.5.12026-07-23T16:58:30+00:00Small change in scope of variables in repeat-until2026-07-23T16:58:30+00:00Roberto Iroberto@inf.puc-rio.br2026-07-23T16:58:30+00:00urn:sha1:7579fc9d7ed90240487251dfb69168f8e64e9294
A close instruction is still inside the scope of the variables it is
closing. The extra close in a repeat-until (to close variables before
repeating the loop) was being coded outside that scope.
Details2026-07-22T16:43:40+00:00Roberto Iroberto@inf.puc-rio.br2026-07-22T16:43:40+00:00urn:sha1:d5bbe955840c5c83e37ed19df4d392d7ba0970ed
- Some api_checknelems changed to the more restrict api_checkpop.
- Added a class to the html for APIs in the manual.
- Comments and manual.
Avoid casts to 'union GCUnion*'2026-07-21T19:51:04+00:00Roberto Iroberto@inf.puc-rio.br2026-07-21T19:51:04+00:00urn:sha1:9130ceb19d324472d135e8e644a01e8b16334c31
The union may have alignment requirements stricter than some of its
members. Some checking tools (e.g., gcc with options -fsanitize) can
then complain that the result of a cast from pointer to member to
pointer to the union is misaligned.
MacOS by default uses statically linked readline2026-07-15T18:39:07+00:00Roberto Iroberto@inf.puc-rio.br2026-07-15T18:39:07+00:00urn:sha1:84938a7d2b680d2d28ec99606e84fe712efd9a69
(plus detail in the manual)
Removed compiler option LUA_COMPAT_LOOPVAR2026-07-13T18:18:37+00:00Roberto Iroberto@inf.puc-rio.br2026-07-13T18:18:37+00:00urn:sha1:6ca33260d26f1b8fab982b13c89de1f445361328
It makes loop variables read-only, but it does not restore the old
semantics, so it is not helpful for compatibility.
Bug: Issues with write barrier for __newindex2026-07-12T17:57:55+00:00Roberto Iroberto@inf.puc-rio.br2026-07-12T17:57:55+00:00urn:sha1:b996f8fd1be7fb711cc6f754a31a1c87d2c2fd9b
In 'luaV_finishset', there is an update on a table that is a field on
another table. If the first table is the same as the one with the field
(e.g., after 't.__newindex = t'), the update can change the value on
that field (e.g., there may be a collision and the field is moved, or
the field being updated is '__newindex' itself). After that, the
barrier is called with the table stored in that field, which is not
the correct table anymore.
Bug: 'luaL_newmetatable' used in a wrong way2026-06-17T14:20:10+00:00Roberto Iroberto@inf.puc-rio.br2026-06-17T14:20:10+00:00urn:sha1:bc4bbcef651ba2870d6c68db16dc7d6ce6f68636
The call to 'luaL_newmetatable' in 'newbox' can leave an incomplete
metatable in the registry, if 'luaL_setfuncs' raises a memory error.
Removed unused function 'luaD_inctop'2026-06-03T14:58:39+00:00Roberto Iroberto@inf.puc-rio.br2026-06-03T14:58:39+00:00urn:sha1:40b76de2d77e66b70a9d4bf989c3f5340919973f
Commit 3228a97 removed all its uses.
Cleaning 'luaP_isIT' and 'luaP_isOT'2026-05-28T18:10:17+00:00Roberto Iroberto@inf.puc-rio.br2026-05-28T18:10:17+00:00urn:sha1:0465c23b3ee214ea3a117ab9d69a83cf85e7a82f
- 'luaP_isOT' is only used for tests, so it is defined as a macro to avoid
wasting space with an unused function.
- 'luaP_isIT' must include OP_VARARGPREP.
Avoid warning in some compilers2026-05-08T18:01:59+00:00Roberto Iroberto@inf.puc-rio.br2026-05-08T18:01:59+00:00urn:sha1:53b41d0cddd80bf33fdc631bdd32e3ba53842b89
In function 'funcargs', some compilers can complain that 'args' can be
used unitialized, due to the default case (syntax error).