Beefy Boxes and Bandwidth Generously Provided by pair Networks
Welcome to the Monastery

Comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

While 90% of the time you may not have to worry about special cases, if you find the need to , you'll have to do a lot of code modification in order to get the special case to work.

Most of the items that Fatal is advertised for only return a "success/fail" value so it is completely trivial to handle the 10% cases. If you look at the return value, then the call isn't fatal. If you don't look at the return value, then the call is fatal.

Calls that return vital information that can also be an error indication aren't as well suited for the type of error handling change that Fatal imposes and so I don't include those in my proposal above. Note that some of the calls do return information, but that information is not vital.

For example, I don't include fork because there usually isn't much point in calling fork in a void context. Since you pretty much have to check the return value from fork (to decide if you are now the parent or the child), you usually also manage to check for the error case. The value returned by fork is "vital".

Now, some invocations of open can return interesting information, such as a process ID. But that information isn't vital. It is very common to check the return value of open only for whether it failed or not. And people (unfortunately) often use open in a void context. So making open (in a void context) "fatal" can be a great way to find hidden errors.

        - tye (but my friends call me "Tye")

In reply to (tye)Re3: use Fatal; by tye
in thread use Fatal; by cLive ;-)

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, 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, 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.
  • Log In?

    What's my password?
    Create A New User
    and all is quiet...

    How do I use this? | Other CB clients
    Other Users?
    Others lurking in the Monastery: (9)
    As of 2018-06-22 19:15 GMT
    Find Nodes?
      Voting Booth?
      Should cpanminus be part of the standard Perl release?

      Results (124 votes). Check out past polls.