The idiom I've normally used is more along the lines of something like this; call open then use constants from Errno to figure out from !$ what specifically went wrong and give more detailed advice. You can also use a variation on this to (e.g.) try and open a file for reading and fall back to another default location if !$ == ENOENT because it didn't exist; (EDIT) or you don't care if it didn't exist, but other errors you do want to bring to the user's attention.
use Errno qw( :POSIX );
use Log::Log4perl;
## ...
if( open( my $fh, q{<}, $filename ) ) {
my $frobulated_data = {};
## process with $fh
close( $fh );
return $frobulated_data;
} else {
if( $! == ENOENT ) {
ERROR( qq{Couldn't find file '$filename': $!} );
} elsif( $! == EACCES ) {
ERROR( qq{Problems with permissions for '$filename': $!} );
} elsif( ## whatever else specific you want to handle ... ) { #...
} else {
ERROR( qq{Problem opening '$filename': $!} );
}
return;
}
The cake is a lie.
The cake is a lie.
The cake is a lie.
-
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.
|