in reply to Re^6: Win32::Job::watch vs. system(1,...)
in thread Win32::Job::watch vs. system(1,...)

Okay. Looking back at the code on my archive CD from my old machine, the one time I had occasion to use Win32::Job, I encountered the same problem and fixed it by adding these 5 lines to Job.xs:

void run_nw(self) JOB_T self CODE: resume_threads(aTHX_ self->procs );

If you add that and rebuild, you can start the job asynchronously by calling $job->run_nw when you've set the job up.

Sorry for not putting two and two together from your earlier posts ... um, earlier.


Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP PCW It is as I've been saying!(Audio until 20090817)