in reply to External controlling of a multi-threaded Windows perl program

If you're doing a GUI it's a good idead to keep it in a thread of its own.

Create a thread first and don't load any GUI modules at all before that, then build the GUI and run main event loop in that one.

Use things like Thread::Queue or Thread::Queue::Any to communicate between the threads.

/J

  • Comment on Re: External controlling of a multi-threaded Windows perl program

Replies are listed 'Best First'.
Re^2: External controlling of a multi-threaded Windows perl program
by weismat (Friar) on Nov 02, 2007 at 14:36 UTC
    I am using Thread::Queue already. Most of my multithreaded modules use this module. Only if I need real two-way communication, than I use the cond_wait and cond_signal. I have some experience with POSIX threads and the queue implementation in Perl is really elegant.