Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
With regards to STDERR trapping, I would direct you to the node How can I capture STDERR from an external command? or Capture Error Messages to a File? How? or even how do i redirect STDOUT, STDIN, or STDERR to a FILE? - All found through the beast that is Super Search.

With error handling, I think your best option may be to execute your perl code within a eval statement and examine the value of $@ upon exit from the scope. I would suggest you to have a read through "Error Indicators", also on the perlvar page (right down the bottom).

 

Ooohhh, Rob no beer function well without!


In reply to Re: "Exception" handling and more... by rob_au
in thread "Exception" handling and more... by r.joseph

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.