You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello TsT !
My idea is to use it in production.
The case of 1/0 base index is still there LJS/LjsJIT is 1 based index right now, because this way it's easy to port existing Lua code for testing, in fact I'm finishing now Openresty and Torch, this way I can verify that my changes do not make the language buggy.
As a second stage probably a 0 index based version will come to light, I'm thinking how that can be implemented in a way to make easy to have mainly extensions usable on both Lua/LuaJIT and LJS/LjsJIT .
Probably having some macros/inline functions to hide the conversion in C/Lua code:
Hello,
I wonder what is your goal for the ljs project.
IMHO, the Lua syntax is not really sexy at all but I'm using it without problem.
I'm still looking about alternative, like moonscript, etc.
I thought (like your project) to using different language syntaxes to execute on the Lua VM (in fact in the LuaJIT one).
There is some case where the usual way to code is complicated to make abstraction.
For sample,
How to you deal with the first array's index is 1 in Lua VS 0 in JS ?
VS
Regards,
The text was updated successfully, but these errors were encountered: