alright, posting a reply here because i think the thread is the right one.
It naturally bumps from these threads, that i don't want ot go off topic
http://www.eqemulator.net/forums/vie...4b1e04e71c133e
http://www.eqemulator.net/forums/vie...4b1e04e71c133e
The general perl process in EQEMu atm is having a callback called when an event is triggered, and this callback does some perl code running, and pushes one or more commands on a queue. Commands are then processed from the queue, after the perl callback has returned. Is that correct ?
Unless big rework is done of the perl quest system, there is little chance to go into calling C from perl (appart some stand-alone library modules), as this would lead to uncontrollable loops or deadlocks, and such stack switching is additional overhead.
The current process leads to exporting more variables as quests require them. It can be optimized, but should'nt be workaround'd
This is just personnal opinion, and i like to get more of your forethoughts on perl quest system.
Threaded Mode
