You might find this subthread useful, but do read the whole subthread.
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco.
Rule 1 has a caveat! -- Who broke the cabal?
| [reply] [d/l] |
No clean way that I know of, to kill a thread.
Here is a link to some PM discussion of a usable, but ugly option.
"There are only two truly infinite things. The universe and stupidity, and I'm not too sure about the universe"- Albert Einstein
| [reply] |
All,
I came up with a solution...not the prettiest, but it works.
First, create a wrapper for launching executables, using Win32::Job. Use Win32::Job's run() function to implement the timeout. Launch this wrapper from the main application, which captures the output.
The use of Win32::Job limits this to the Win2K+ platforms...but for now, that's not really a big issue.
Thanks!
| [reply] |