@techee > But I suspect users of this plugin will use it for smaller utilities related > to their workflow and they won't use any advanced features from the language > where they might see differences.
(@elextr chuckles to self) Of course that argument could be run backwards, if scripts won't use the newer features there is no _Lua_ reason to upgrade :grin: Your comments on possible performance issues are valid, compiling first every time a script is run _may_ be slower than interpreting for short scripts, but IIUC there is a compile cache so a function only gets compiled once. What the effect is can only be determined by benchmarking lots of Geanylua scripts, but we don't have those, and no Geanylua users have commented on this issue's issues. Maybe there are no intensive users, only occasional users like @xiota so nobody will care about such details. For example it seems (#1236) that `grabkey()` has not been working for an unknown period of time, but nobody has complained? Dunno. @xiota > Adding LuaJIT build support now doesn't in and of itself block work toward > supporting another Lua release in the future. True, and #1235 suggests the changes are simple enough that both 5.1 and 5.4 C APIs could be supported within the `#ifdef` pain threshold. As a wise man once said, if offered a questionable choice, take all three (at least until a winner is clear). -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany-plugins/issues/1133#issuecomment-1455359989 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany-plugins/issues/1133/[email protected]>
