Thanks. You are right. Examining $? helps to know if the child process executed correctly or not.

Here my sample code:

eval
{
    open my $pipe, "perl --version |";
    my @res = <$pipe>;
    close $pipe;
};

print "Exit Status: " . ($?>>8);

[download]

If I use the not existing command "perl2 --version" then I get the following error message and the exit status 1.

Der Befehl "perl2" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Exit Status: 1

[download]

If I use an existing command like "perl --version" then I get the exit status 0 and no error message:

Exit Status: 0

[download]

Problem of course is that I then know the error not directly after the open, but only when the child process exited, that means after the close.

In reply to Re^4: Opening not-existing command - Error Handling by Dirk80
in thread Opening not-existing command - Error Handling by Dirk80

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.