Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

comment on

( [id://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 ;-)

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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others studying the Monastery: (3)
As of 2024-03-29 01:39 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found