Below are some examples of "die" messages on my Windows machine for a non-existent file. I used "warn" instead of "die" so that all 4 examples would run.

In the first example, I just have the OS error code $!. Well if the code is opening many files, "which file?" is not known - although you can get the Perl source line that the error occurred on. I don't expect users to have to look into the code so that isn't ideal.

The second example, I put the filename that was trying to be opened into the "die" message. That is often way more useful than the OS error code alone. Usually not to hard to figure out why that file couldn't be opened.

In the third example, I put both the filename and error code. I most often include both pieces of information. Also note that I also put whether a read, write or append was attempted into the error message.

In the fourth example, I suppress the output of the Perl source line number by simply appending a "\n" to the "die" string. In a lot of situations, the user doesn't care about this Perl code line and it just clutters things up and can confuse folks. 

#!/usr/bin/perl -w
use strict;

my $infile = 'bogus_name';

open IN, '<', $infile or warn "$!";

# No such file or directory at C:\TEMP\demoOpenMessage.pl line 6.

open IN, '<', $infile or 
     warn "cannot open $infile for reading";
     
#cannot open bogus_name for reading 
# at C:\TEMP\demoOpenMessage.pl line 6.
         
open IN, '<', $infile or  
     warn "cannot open $infile for read-> $!";

#cannot open bogus_name for read-> No such file 
#   or directory at C:\TEMP\demoOpenMessage.pl line 12.

open IN, '<', $infile or  
     warn "cannot open $infile for read-> $!\n";
     
#cannot open bogus_name for read-> No such file or directory

[download]

In reply to Re^3: Newby question by Marshall
in thread Newby question by Parmenides

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.