-
Notifications
You must be signed in to change notification settings - Fork 199
Lua 5.1 compatibility #798
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks for an invitation.
|
@ildar thank you for review
|
on (2): plz take a look:
lunarmodules/lua-compat-5.3@7e2b0b5
|
oh, so similar to bitop, i'll consider re-working the PR eventually, thank you would it somehow be even possible to backport the bitwise operators (eg. |
on (1) I just read the whole discussion. I perceive @GreyCat sympathised
Dual-lua-targeting, calling it cross-platform-ing later:
kaitai-io/kaitai_struct_lua_runtime#1 (comment)
I suggest suporting dual/triple-Lua-versions as:
1. it looks like there are users for 5.3, 5.1 and even 5.2 (rare in the
Lua community yet demanded because of WShark);
2. it corresponds to current Lua community trends as many Lua libraries
are 5.1 and 5.3 compatible (check LuaRocks.org)
One added issue to solve is testing: Kaitai would better be tested with all
2 (or 3) Lua versions. But this IMHO could be postponed for a later fix.
|
Final solution should be compatible 5.1+ and agree, so i'll update ci_targets with matrix of testing for each specific lua version |
This PR is closed since the individual submodules will get updated anyway |
bit
libraryxpcall
in Lua5.1 takes 2 args instead of varargsThis is also related to PR kaitai-io/ci_targets#7