IMHO, the suggestions put forward thus far, whilst returning the status code back to the calling script, don't appear to address
leonidlm's interest in the output from the called batch script - so why not just use backticks. That way, you gain access to the return code (via
$?) and the output (via the return from the backtick invocation) e.g.
my $output = `batch_file args`;
die "Gone horribly wrong - $?" if $?;
# or ...
my @output = `batch_file args`;
die "Gone horribly wrong - $?" if $?;
.oO(Unless, of course, Windoze sees fit to not return the status code from the batch script, in which case...)
my $output = `batch_file args && exit /b ERRORLEVEL`;
die "Gone horribly wrong - $?" if $?;
# or ...
my @output = `batch_file args && exit /b ERRORLEVEL`;
die "Gone horribly wrong - $?" if $?;
,or something similar, may suffice ... unless I'm missing something obvious?!
Sits back and awaits flames, errm, constructive observations ;-)
HTH ,
At last, a user level that overstates my experience :-))
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.