There's no "problem" to "solve", per se.

* Changing `luaL_reg` to `luaL_Reg` would make for one less thing to fix 
when/if switching to a different Lua release, whether 5.4+ or LuaJIT.
* LuaJIT performs better, even with JIT turned off.  Probably doesn't matter 
much for Geany.
* Switching to something else improves the chances of GeanyLua becoming 
maintained.  Those with Lua 5.1 expertise have likely moved on to later 5.x 
releases or LuaJIT.  Those without existing expertise are more likely to be 
willing to learn 5.4+ or LuaJIT.
* Since LuaJIT is a drop-in replacement for Lua 5.1, switching back and forth 
wouldn't be difficult.  The `build/*.m4` script might even be able to detect 
and support both.
* LuaJIT supports macOS, so it might be possible to make the currently 
non-existent (Intel) macOS version of the plugin exist.  To workaround the 
ARM64e issue, Lua 5.1 could be used, if it works.  If not, it's a wash and 
there is no "sacrifice" either way.  Since LuaJIT is maintained, there's a 
reasonable chance the issue will be fixed sometime around when mainline Linux 
fully supports Apple M# processors.
* LuaJIT has some interesting features of its own, but that could break Lua 5.1 
compatibility.
* Lua 5.1 is at risk of being dropped someday.  Maybe not for another two 
decades, but the number of packages that use it is dwindling.  In the distro 
I'm currently using, there are seven packages that depend on Lua 5.1, after 
excluding Lua 5.1 and modules.  I recall that there were more in the past.  At 
least one appears to have dropped Lua support entirely, rather than migrate.  
LuaJIT is almost as popular as Lua 5.4.  There are nearly three dozen packages 
using LuaJIT, including gegl, mpv, obs, and vlc.  There are over three dozen 
packages using Lua 5.4, while Lua 5.2 and 5.3 are unused.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/1133#issuecomment-1454277806
You are receiving this because you are subscribed to this thread.

Message ID: <geany/geany-plugins/issues/1133/[email protected]>

Reply via email to