lua-users home
lua-l archive

[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index] [Thread Index]

Thanks Mike for your help, but I can't proceed as you advise, because I have to somewhat patch LuaJIT to completely integrates it to our application: for instance we have a debugger that is triggered when an error occurs, but before the stack is unwind so we can see the call stack and local variables across it. Another problem is that we have to trap the output of the print() command to redirect it to the application unified console. An a last example with the os.exit() command that is modified to just stop the script execution and not kill the application :-). We had these problems previously with the regular Lua and this has nothing to do with LuaJIT. Maybe a possible solution would be to have a standard hook API for those feature. I saw that some people discussed about this for the debugger error interception.

Anyway, I have to do this. To minimize the risk of doing errors, all the VM part is generated by your script, and the rest is integrated via amalg.c so I only have one file where I have to care about the compiler settings. So far it works very well (until now).


Ingénieur Système / System Engineer

Tél: +33 (0)1 53 66 39 89
Fax: +33 (0)1 43 76 91 25

ART Technology
Le Chanzy
18 avenue Winston Churchill