Goals of LuaJIT and compatibility

[David Demelier]

Hello,

I'm new on this list and also new in LuaJIT world.

I've recently gave up using vanilla Lua because of the authors decisions
to remove existing features and design changes. Like removing math
functions or the __ipairs metamethod (which now needs to implement both
__index and __len as a function).

So I was thinking about moving to LuaJIT because it seems to keep
compatibility. However, I can not find the goals of LuaJIT especially :

Will new releases follow the new versions of Lua ? Like Lua 5.3 and its
removal __ipairs, math and such.

Kind regards,
David.

[Coda Highland]

Post by David Demelier
Hello,
I'm new on this list and also new in LuaJIT world.
I've recently gave up using vanilla Lua because of the authors decisions to
remove existing features and design changes. Like removing math functions or
the __ipairs metamethod (which now needs to implement both __index and __len
as a function).
So I was thinking about moving to LuaJIT because it seems to keep
Will new releases follow the new versions of Lua ? Like Lua 5.3 and its
removal __ipairs, math and such.
Kind regards,
David.

You can be compatible with 5.3 without removing __ipairs and the math
functions -- and doing so would help preserve compatibility with 5.1
and 5.2.

As such, I see it being very unlikely that such breaking changes would be made.

/s/ Adam

[Roman Tsisyk]

Post by David Demelier
Will new releases follow the new versions of Lua ? Like Lua 5.3 and its
removal __ipairs, math and such.

I wonder which feature from Lua 5.3 do you need?

[David Demelier]

Post by Roman Tsisyk

Post by David Demelier
Will new releases follow the new versions of Lua ? Like Lua 5.3 and its
removal __ipairs, math and such.

I wonder which feature from Lua 5.3 do you need?

I don't need anything, it's quite the opposite, Lua 5.3 removed (or
actually deprecated) feature from the Lua 5.2 like __ipairs and math
functions. That's why I'm thinking using LuaJIT instead if it is sure
that backward compatibility is a primary goal.

Regards,
David.

[Elias Hogstvedt]

I personally hope that LuaJIT will be able to follow most or all Lua
changes. I imagine it's going to try to follow it.

But if your only concern are deprecated features you might as well just
stick to 5.1 (or 5.2?) instead of switching to LuaJIT.

It sounds to me like you want to switch sides rather than language.

Post by David Demelier

Post by David Demelier
Will new releases follow the new versions of Lua ? Like Lua 5.3 and its
removal __ipairs, math and such.
I wonder which feature from Lua 5.3 do you need?

I don't need anything, it's quite the opposite, Lua 5.3 removed (or
actually deprecated) feature from the Lua 5.2 like __ipairs and math
functions. That's why I'm thinking using LuaJIT instead if it is sure that
backward compatibility is a primary goal.
Regards,
David.