I'm planning to create a super-set of Lua called Lua Lux (Moonlight)*, and it'll feature close tie-ins with the OpenCL (when ATi/NVidea/Intel/AMD get their act in gear!) portion of the engine. I'm not expecting Decoda to reach into the OpenCL-Lua-ed parts of the engine (seperate states with some restrictions, etc..), but I would like to know how far I can stretch the elastic band, and in what directions, before it snaps and viciously hurts me. The things I hope to add are partially syntactically based (no problems here), a few new opcodes for various things (here??), and a few other little goodies (userdata/metamethod stuff, no problems here).
Also, how well would Decoda handle multiple states all using one environment? Would it have a seizure and die, or would it just shrug and keep moving? Need to know before I unintentionally sabotage my only debug tool other then print. That and the fact that it would require quite a bit of redesigning...
PS: The 'Toggle Side Panel' doesn't work for me? Anyone else? PPS: The bug where you can't open a non-project-ed Lua file with the same name as one which is Project-ed (because it opens the project one instead, even when you open it via double click in explorer), is still around. Could you fix it? Pretty please?
* Because my engine is called Aeterna, i.e. Eternal Moonlight... Yah I know it sucks. And yes I know I'm mixing Latin and Portugese!
Post edited by Unknown User on
karajorma: Okay. I'm gonna go raise my blood pressure a little then post