> The code did not change (except for the type of 'hookmask' that, as I mentioned, went from 'lu_byte' to 'l_signalT'). I simply added an explanation of why the code as it is should work.
Shouldn't we have a note to that effect in the reference manual, too?
Something like "breaking into executing Lua code can be achieved by calling lua_sethook from a signal handler or from another thread, which, unlike other Lua API calls, allows that without additional synchronization"?
