I'd probably use a Win32::Semaphore for the signal.
use Win32::Semaphore; my $sem = new Win32::Semaphore(0,1) ... if( my $code_pid = fork() ) { sleep(5); $sem->release(); } elsif( defined $code_pid ) { print "Process executing.."; _spin(); bless $sem, 'do not destroy'; exit 0; ... sub _spin { SPIN: while(! $sem->wait(0)) { ...
The bless $sem, 'do not destroy'; hack is necessary because the fork() did not create a new process, but a new thread under Windows and if you allowed Win32::Semaphore to do proper destroy you'd destroy even the parent's object. (The $sem objects in both threads share the same handle to the semaphore.)
Another option would be to start using "proper" threads. (See perldoc threads. That would allow you to share variables between threads.
HTH, Jenda
In reply to Re: Child reading from Parent
by Jenda
in thread Child reading from Parent
by icius
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |