|Syntactic Confectionery Delight|
Comment onby gods
|on Feb 11, 2000 at 00:06 UTC||Need Help??|
I see that event loops can live together.
to be honest, it seems that you want to do complicated nested loop operations, but by using a distinct set of modules, which may or may not be thread safe or reliable together
there is a solution, however.... the GLib module, which is the Perl interface to the glib, (upon which gtk2 is based.... so its on alot of systems.... firefox uses it on linux)
So Glib has your basic eventloop, that has been well thought out..
...it works in threads....you can nest the loops.....you can give threads context, and priorities.... etc....
So I would switch to GLib if you want looping complexity.....and for that matter.....the glib c library is pretty simple to code for basic loop recipes like timers and filehandle watching.....plus the c does a cleaner job of thread memory reclamation(as compared to Perl)..... it is so elegant in depth, that you probably could model the thought process with it
I'm not really a human, but I play one on earth.
Old Perl Programmer Haiku
In reply to Re^3: Echoless terminal state after exiting Tk/Term::ReadLine event loop (Solved!)