colonelthirtytwo / luajit-async Goto Github PK

Simple, small and smart is your solution as it is your GLWF binding (which I have used alot)

I have added a "init" argument which is a function to be executed once to make some requires and other initialization stuff for the callbacks.

Threads are only for windows but I see you have LuaJIT-Threads (which has a small compiled file) Shouldn't both projects be merged?

The only thing I am missisng is interstates comunication (which can be solved with socket or zmq) but I am curious about what you mean with:
"The only way to share information between the main Lua state and the callback is by a
userdata pointer in the callback function, which you will need to synchronize yourself."

could you provide an example? (without syncronization)

Thanks
victor bombi

Hello Alex,

I have been using this without problems alot of time in win32 32bits and 64bits.

Last day I had acces to an ubuntu machine ( I am newcommer to linux) and the callback test (from your branch also) says: Segmentation fault.

Any clue to someone new to linux that could explain that?

Thanks for you patience
victor bombi

Analyzing the source code: 1 warning.
lj-async/thread.lua:64:15: accessing undefined variable 'str_b'