[ANN] Lua 5.3.5 (rc1) now available

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

[ANN] Lua 5.3.5 (rc1) now available

Luiz Henrique de Figueiredo
Lua 5.3.5 (rc1) is now available at
        http://www.lua.org/work/lua-5.3.5-rc1.tar.gz

The checksums are
        MD5     806451f2c6903da7696822a44892e47d  -
        SHA1    585945837460e8b5f67cc3a5b208f838cde53136  -

Lua 5.3.5 fixes all bugs listed in http://www.lua.org/bugs.html#5.3.4 .

Like all minor releases, this is strictly a bug-fix release: no new
features or improvements have been added.  The reference manual has
been updated.

This is probably the last release of Lua 5.3. Now is the time to
report glitches and to try to fix any remaining bugs.

The complete diffs from Lua 5.3.4 are available at
        http://www.lua.org/work/diffs-lua-5.3.4-lua-5.3.5.html
        http://www.lua.org/work/diffu-lua-5.3.4-lua-5.3.5.html

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

All feedback welcome. Thanks.
--lhf

Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Lua 5.3.5 (rc1) now available

Javier Guerra Giraldez
> may be classified as equal or not
> (depending on internal cashing details).

cashing?  caching?  cacheing?  something completely different?

--
Javier

Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Lua 5.3.5 (rc1) now available

Thijs Schreijer
In reply to this post by Luiz Henrique de Figueiredo


> On 25 Jun 2018, at 19:50, Luiz Henrique de Figueiredo <[hidden email]> wrote:
>
> Lua 5.3.5 (rc1) is now available at
>        http://www.lua.org/work/lua-5.3.5-rc1.tar.gz
>
> The checksums are
>        MD5     806451f2c6903da7696822a44892e47d  -
>        SHA1    585945837460e8b5f67cc3a5b208f838cde53136  -
>
> Lua 5.3.5 fixes all bugs listed in http://www.lua.org/bugs.html#5.3.4 .
>
> Like all minor releases, this is strictly a bug-fix release: no new
> features or improvements have been added.  The reference manual has
> been updated.
>
> This is probably the last release of Lua 5.3. Now is the time to
> report glitches and to try to fix any remaining bugs.
>
> The complete diffs from Lua 5.3.4 are available at
>        http://www.lua.org/work/diffs-lua-5.3.4-lua-5.3.5.html
>        http://www.lua.org/work/diffu-lua-5.3.4-lua-5.3.5.html
>
> We thank everyone for their feedback on Lua 5.3 till now.
>
> All feedback welcome. Thanks.
> --lhf
>

Fyi Just gave it a quick test, LuaWinMake [1] will build this without any changes with both MS as well as GCC based toolchains. No warnings, just works as expected.

Thijs


[1] https://github.com/Tieske/luawinmake
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Lua 5.3.5 (rc1) now available

Andrew Gierth
In reply to this post by Luiz Henrique de Figueiredo
>>>>> "Luiz" == Luiz Henrique de Figueiredo <[hidden email]> writes:

 Luiz> Lua 5.3.5 fixes all bugs listed in http://www.lua.org/bugs.html#5.3.4 .

So a question that comes to mind is this: why is there no sane way for
the host program to detect the Lua minor version either at compile time
or runtime? In my code I have to expend a _lot_ of effort on a
workaround for one of the 5.3.4 bugs, but there's no good way for me to
detect whether I'm actually building against 5.3.5 in order to skip
doing that.

(The only record of the minor version seems to be LUA_VERSION_RELEASE,
which is a string and not a number so it can't be used for conditionals
without doing ugly makefile tricks.)

What I _want_ to be able to do is something like:

#if LUA_VERSION_NUM == 503 && LUA_VERSION_RELEASE_NUM < 5
#define USE_BUG_WORKAROUND
#endif

and later,

#ifndef USE_BUG_WORKAROUND
    int lua_ver = lua_version_release(L);
    /*
     * if we're not using the workaround, check that we don't have the
     * bug.
     */
    if (lua_ver >= 50303 && lua_ver < 50305)
        luaL_error(L, "Recompile with correct lua version");
#endif

But without minor version checks, I'm stuck having to use the workaround
all the time whether it's really needed or not.

--
Andrew.

Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Lua 5.3.5 (rc1) now available

Egor Skriptunoff-2
On Tue, Jun 26, 2018 at 2:32 PM, Andrew Gierth wrote:

So a question that comes to mind is this: why is there no sane way for
the host program to detect the Lua minor version either at compile time
or runtime?

#ifndef USE_BUG_WORKAROUND
    int lua_ver = lua_version_release(L);
    if (lua_ver >= 50303 && lua_ver < 50305)
        luaL_error(L, "Recompile with correct lua version");
#endif


Host program should be able to read lua_ident[0] (declared in "lua.h") to detect Lua release in runtime.
This is a string, not a number.
Reply | Threaded
Open this post in threaded view
|

Re: [ANN] Lua 5.3.5 (rc1) now available

Philipp Janda
Am 27.06.2018 um 21:08 schröbte Egor Skriptunoff:

> On Tue, Jun 26, 2018 at 2:32 PM, Andrew Gierth wrote:
>
>>
>> So a question that comes to mind is this: why is there no sane way for
>> the host program to detect the Lua minor version either at compile time
>> or runtime?
>>
>> #ifndef USE_BUG_WORKAROUND
>>      int lua_ver = lua_version_release(L);
>>      if (lua_ver >= 50303 && lua_ver < 50305)
>>          luaL_error(L, "Recompile with correct lua version");
>> #endif
>>
>>
> Host program should be able to read lua_ident[0] (declared in "lua.h") to
> detect Lua release in runtime.
> This is a string, not a number.

There is also `LUA_VERSION_RELEASE[0]` which is a `char`, but also
requires runtime dispatch (or maybe not in C++?). That's the one I use
to set certain function pointers during initialization.

Philipp