[ANN] Lua 5.4.7 (rc1) now available

[Luiz Henrique de Figueiredo]

Lua 5.4.7 (rc1) is now available for testing at
https://www.lua.org/work/lua-5.4.7-rc1.tar.gz

The SHA256 checksum is
9f51aeeaba66df34df7b63dfb8f94cb33000aad4d8788f66ac913a9efb5a64f7 -

Lua 5.4.7 fixes all bugs listed in
https://www.lua.org/bugs.html#5.4.6

Lua 5.4.7 also contains internal improvements and a revised reference manual:
https://www.lua.org/work/doc/

The complete diffs from Lua 5.4.6 are available at
https://www.lua.org/work/diffs-lua-5.4.6-lua-5.4.7.html
https://www.lua.org/work/diffu-lua-5.4.6-lua-5.4.7.html

We thank everyone for their feedback on Lua 5.4 till now.

All feedback welcome. Thanks.
--lhf

[Andrew Trevorrow]

> All feedback welcome. Thanks.

Minor typos in some comments:

Replace "sufix" with "suffix" in lua.c (twice) and

in luaconf.h (once).

Andrew

[bil til]

Am Fr., 10. Mai 2024 um 22:32 Uhr schrieb Luiz Henrique de Figueiredo
<l...@tecgraf.puc-rio.br>:

>
> Lua 5.4.7 (rc1) is now available for testing at
> https://www.lua.org/work/lua-5.4.7-rc1.tar.gz

> --lhf

One question if allowed: Is the Lua binary file (compiled by luac) now
made such, that all function chunks start 32bit aligned against file
start?

(so that in Microcontroller applications with restricted RAM, the
function code can be kept in ROM / loaded directly from ROM without
big problems / source code changes - this would be super-great /
RAM-saving?)

[blog...@gmail.com]

>Lua 5.4.7 (rc1) now available

Yaaaa.

суббота, 11 мая 2024 г. в 08:39:47 UTC+3, bil til:

[Roberto Ierusalimschy]

> Minor typos in some comments:
> Replace "sufix" with "suffix" in lua.c (twice) and
> in luaconf.h (once).

Thanks.

-- Roberto

[Roberto Ierusalimschy]

> One question if allowed: Is the Lua binary file (compiled by luac) now
> made such, that all function chunks start 32bit aligned against file
> start?
>
> (so that in Microcontroller applications with restricted RAM, the
> function code can be kept in ROM / loaded directly from ROM without
> big problems / source code changes - this would be super-great /
> RAM-saving?)

No, binary files must be compatible between releases of the same
version. That reature will only come in the next version, 5.5.

-- Roberto

[Xavier Wang]

Luiz Henrique de Figueiredo <l...@tecgraf.puc-rio.br> 于2024年5月11日周六 04:32写道：
> All feedback welcome. Thanks.

The manual of `lua_toclose` has a sign of `[-0,+0,m]`, but It seems
may throw a runtime error when the slot doesn't have `close`
metamethod, so it should be `e` or `v` instead `m`?

--
regards,
Xavier Wang.

[Roberto Ierusalimschy]

> The manual of `lua_toclose` has a sign of `[-0,+0,m]`, but It seems
> may throw a runtime error when the slot doesn't have `close`
> metamethod, so it should be `e` or `v` instead `m`?

Right. Thanks for the feedback. (BTW, it cannot throw a memory error.)

-- Roberto

[Lourival Vieira Neto]

Is it possible to have git tags for the release candidates? It would
make it a lot easier to validate the changes against Lunatik =).

Thanks,
--
Lourival Vieira Neto

[Roberto Ierusalimschy]

> Is it possible to have git tags for the release candidates? It would
> make it a lot easier to validate the changes against Lunatik =).

rc1 is commit de794a6527058e75b674118b35f39dcbb13e88b1.

-- Roberto

[Lourival Vieira Neto]

Thank you!

--
Lourival Vieira Neto