[ANN] Lua 5.4.8 (rc1) now available

[Luiz Henrique de Figueiredo]

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

The SHA256 checksum is
4f18ddae154e793e46eeab727c59ef1c0c0c2b744e7b94219710d76f530629ae  -

The Git commit ID in branch v5.4 is
6e22fedb74cf0c9b6656e9fce8b7331db847c605

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

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

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

All feedback welcome. Thanks.
--lhf

[Benoit Germain]

Hi all,

Built with gcc 15.1.0 for msys2 ucrt64, no warning.

Built with Microsoft VisualStudio.17.Release/17.13.7+36105.23, both for Win32 and x64, no warning.
All Lanes 4.0 unit tests pass successfully against Lua 5.4.8.

Regards,

Benoit.

--
You received this message because you are subscribed to the Google Groups "lua-l" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lua-l+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/lua-l/d7a81969-2262-469b-9121-27dae4c06b39n%40googlegroups.com.

[Luiz Henrique de Figueiredo]

> Built with gcc 15.1.0 for msys2 ucrt64, no warning.
> Built with Microsoft VisualStudio.17.Release/17.13.7+36105.23, both for Win32 and x64, no warning.
> All Lanes 4.0 unit tests pass successfully against Lua 5.4.8.

Thanks for the report.

[Luiz Henrique de Figueiredo]

Lua 5.4.8 (rc1) is available for testing at
https://www.lua.org/work/
Please try it before we freeze it.

If there is no further feedback on Lua 5.4.8, we'll freeze it next week, and it will become the current release of Lua 5.4.

[blog...@gmail.com]

Trying on Debian 13  (amd64)

just gcc  and musl-gcc (Debian 14.2.0-19) 14.2.0

All my applications as precompiled bytecode from 5.4.5/5.4.7 works fine  :)

And my application packer lua app script + lua host source + musl-gcc =  single undepended exacutable application works fine too :) 

But not compile with tcc 

   https://paste.debian.net/1377083/

It nevermind, Im  just notice about it :) For compile with tcc need this

```

lua-5.4.8$ make posix CC=tcc AR="gcc-ar cq"

```

Maybe usefull for someone. Im use tcc for test builds, Lua source compilation time with tcc ~0.1 seconds :D Good for experiments

```

dron@gnu:~/lua-5.4.8$ make clean > /dev/null 2>&1
dron@gnu:~/lua-5.4.8$ time make CC=gcc -j6 > /dev/null 2>&1

real 0m3.216s
user 0m11.058s
sys 0m0.708s
dron@gnu:~/lua-5.4.8$ make clean > /dev/null 2>&1
dron@gnu:~/lua-5.4.8$ time make posix CC=tcc AR="gcc-ar cq" -j6 > /dev/null

real 0m0.110s
user 0m0.252s
sys 0m0.125s
dron@gnu:~/lua-5.4.8$

```

Thanks! ^.^

среда, 28 мая 2025 г. в 14:00:44 UTC+3, Luiz Henrique de Figueiredo:

[Xavier Wang]

> If there is no further feedback on Lua 5.4.8, we'll freeze it next week, and it will become the current release of Lua 5.4.
>
> All feedback welcome. Thanks.
> --lhf
>

May some of out of topic. I'm trying the 5.4.8 with onelua.c and try
to bundle another C++ library into standard library. I was surprised
to find that the code failed.

It's caused by the macro `next` conflict with the C++ `std::next`. It
may only happens when I use onelua.c, renamed it into "onelua.cpp",
and add my own #include for the C++ library source aside with the
standard libraries files.

To workaround it, just add a `#undef next` before the include of my own code.

I have never done this before, only this time to try it with a newer
version. I think it will fail from Lua 5.1 to the latest one.

So maybe it's worth to considering renaming the `next` macro with
another name? maybe `read_next` or something else?

[Luiz Henrique de Figueiredo]

> To workaround it, just add a `#undef next` before the include of my own code.

One Lua is available at https://www.lua.org/extras/ .
It is meant to be used as a single object file liblua.o, instead of liblua.a.
It is not meant to be #included in your source code.

[Warner Losh]

Greetings,

I've dropped this into the FreeBSD tree. Both the boot loader and
other uses we have of Lua work the same between 5.4.7 and 5.4.8rc1.
This isn't an extensive, exhaustive test by any means, but it compiled
out of the box and the 'most demanding' of the things we use Lua for
just worked.

Warner

[Xavier Wang]

> One Lua is available at https://www.lua.org/extras/ .
> It is meant to be used as a single object file liblua.o, instead of liblua.a.
> It is not meant to be #included in your source code.

Got it, thank you!

I just add my own code's include into onelua.c, to make a liblua.o
with my own library bundled. But you right, I could just build them
separated and link together. Thanks for the clarification.

--
regards,
Xavier Wang.

[Tom Sutcliffe]

No issues found compiling LuaSwift for macOS (using Xcode 16.3) and running its test suite, or running a few apps through OpoLua.

Cheers,

Tom