Re^2: question on exitcode provided by status() method of Win32::Job

Thanks for the suggestion. However, I wrote the spawned script and I know what exit codes it returns, and 13 isn't one of them. That's why I posted the question.

I discussed the situation with my boss, and he had me check the version of the Win32::Job Perl module on CPAN. The version number is 0.01, the script was written in 2002, and it's never been updated. So it wouldn't be surprising if the mysterious exit code value were the result of a bug. Therefore, I'm getting rid of the Perl module and writing my own code to do what I need.

Thanks for all the suggestions.

Comment on Re^2: question on exitcode provided by status() method of Win32::Job

Replies are listed 'Best First'.
Re^3: question on exitcode provided by status() method of Win32::Job by BrowserUk (Patriarch) on Nov 17, 2010 at 20:10 UTC
So it wouldn't be surprising if the mysterious exit code value were the result of a bug. Hm. That seems most unlikely. Why would the module place an internal error code in place of the exit code of the script it is calling?	[reply]
Re^4: question on exitcode provided by status() method of Win32::Job by stevehs17 (Novice) on Nov 18, 2010 at 01:38 UTC
"Why would the module place an internal error code in place of the exit code of the script it is calling?" If the module has a bug in it, there's no telling what it will do, even if it's not what the author intended.	[reply]
Re^3: question on exitcode provided by status() method of Win32::Job by bobr (Monk) on Nov 18, 2010 at 16:16 UTC
When I look at CPAN, it looks like latest module version is 0.03, last updated during 2008. I am using it in some my programs and works fine for me. I usually check return value of `run` method to find if it timeed out, though. -- Roman	[reply] [d/l]