I use something like this:
package OpenOrDie;
use strict; use warnings;
use vars '@ISA @EXPORT $VERSION';
require Exporter;
$VERSION = '0.30';
@ISA = 'Exporter';
@EXPORT = 'Open';
sub Open {
my ($mode, $file) = @_;
open my $fh, $mode, $file
or die("Unable to open file '$file' using mode '$mode': $!")
return $fh;
}
Which I then use like:
use OpenOrDie;
my $FILE = Open('<',$filename);
This also means I can catch the error consistently:
eval {
my $FILE = Open('<',$filename);
}; if ($@) {
warn("Cannot parse configuration; $@");
$config{skip} = 1;
}
<-radiant.matrix->
Larry Wall is Yoda: there is no try{} (ok, except in Perl6; way to ruin a joke, Larry! ;P)
The Code that can be seen is not the true Code
"In any sufficiently large group of people, most are idiots" - Kaa's Law
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.