Vadim A. Misbakh-Soloviov
unread,Jul 14, 2022, 9:57:02 AM7/14/22Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Sign in to report message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to openresty-en, LuaJIT
Hi there!
For a long time Mike argued that LuaJIT will stick to 5.1 API/ABI as almost
all the lua software targeting it.
That was really the case, but for now many (if not all) alive projects moves
to 5.2+ and even 5.4.
Even some of them (say, I've read an email from Prosody) even drops 5.1 (and
so LuaJIT because of that) support already.
Isn't it a time to move LJ forward as well?
// btw, that letter is adressed not only to Mike and "upstream" LuaJIT
maintainers, but also to the guys from OpenResty that mainains their "branch"
(and trying to not call it "fork", despite of changes) of LuaJIT.
As many modern libs moves to 5.4 and some of them drops 5.1, and OpenResty
ships with LJ-only (and even spam logs if it is built with "vanilla" LuaJIT,
and not OpenResty fork (let's call things by their names), it gets harder to
use preferred lua libs in development using OpenResty.
Maybe you would consider to implement 5.4 API in LJ on you own, if Mike will
refuse to do that upstream?