I want to put Lua 5.2 in the next release (whatever comes after 1.2.7) to get everyone on the new platform straight away. And to stamp out any incompatibilities early-on.
I like the helpers so the old stuff works… but there’s a part of me that says
function loadstring()
print "loadstring() is deprecated - use load() instead"
end
may be more painful, but better in the long run? I’m just concerned about hidden differences. Dunno. I can see the reasoning behind just making it work as well.
@Bortels - I actually like your solution better. Not keeping up with what is currently “correct” might be a problem some day. Especially since (at least currently), anyone can “correct” the code they might get from someone.
Bingo. Codea isn’t for playing Lua Apps - it’s for making them.
The wrapper code that ‘just works’ would be totally appropriate for a player app, where the user isn’t in a position to fix things. But with the editor there, I want it to tell me I’m using something no longer properly supported - it’ll prevent surprises when I go use my new Lua-hacking skills elsewhere.