lua/lparser.c, 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.
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.
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).
Bug: 'lua_load' does not preserve the stack2026-04-23T20:57:42+00:00Roberto Iroberto@inf.puc-rio.br2026-04-23T20:57:42+00:00urn:sha1:3228a97c6a953dcf397944161bb64b12f1ff5384
'lua_load' does not preserve the stack through the calls to the
reader function, as it should. Immediately after the first call (to
detect whether chunk is binary) it adds stuff, and it also adds a new
table when starting the compilation of each new function.
Some compilation options configurable from makefile2026-01-20T16:06:16+00:00Roberto Ierusalimschyroberto@inf.puc-rio.br2026-01-20T16:06:16+00:00urn:sha1:e992c6a95939c8e1fe357bfce481e0d0c762c3c6
Compilation options LUA_COMPAT_GLOBAL, LUA_COMPAT_LOOPVAR, and
LUA_READLINELIB do not affect the API, so they can be changed
through the make file.
New compile option LUA_COMPAT_LOOPVAR2026-01-16T19:38:44+00:00Roberto Iroberto@inf.puc-rio.br2026-01-16T19:38:44+00:00urn:sha1:f5d1e8639bf5df24c761602354218df21f796a30
When on, this option makes for-loop control variables not read only.
Details2025-12-08T16:09:47+00:00Roberto Iroberto@inf.puc-rio.br2025-12-08T16:09:47+00:00urn:sha1:104b0fc7008b1f6b7d818985fbbad05cd37ee654
- Avoid fixing name "_ENV" in the code
- Small improvements in the manual
Functions with vararg tables don't need hidden args.2025-11-28T18:12:51+00:00Roberto Iroberto@inf.puc-rio.br2025-11-28T18:12:51+00:00urn:sha1:a07f6a824197d7dc01c321599d3bc71936a2590e
Vararg functions with vararg tables don't use the arguments hidden in
the stack; therfore, it doesn't need to build/keep them.
New conceptual model for vararg2025-11-26T14:18:29+00:00Roberto Iroberto@inf.puc-rio.br2025-11-26T14:18:29+00:00urn:sha1:f33cc4ddec886ea499d7d41dd60cac5ddc5687db
Conceptually, all functions get their vararg arguments in a vararg
table. The storing of vararg arguments in the stack is always treated
as an optimization.
Global initialization checks name conflict2025-11-08T14:43:42+00:00Roberto Iroberto@inf.puc-rio.br2025-11-08T14:43:42+00:00urn:sha1:e44f3a2ffc7ced5e75cca7657aaa60ef27da89aa
Initialization "global a = 10" raises an error if global 'a' is already
defined, that is, it has a non-nil value.