My quick & dirty getfile subroutine. And a one liner too, courtesy of Merlyn (with some modifications) ... not sure which would be faster.
Added one after reading Best Practices. I don't know how fast it would be, or if it would be faster. I haven't even syntax checked this. I just wanted to get this down during a quick stop.
Minor fix to the last sample
sub getfile {
my $filename = shift;
open my $FH, "<$filename" or die "Unable to open $filename: $!";
return wantarray ? map /(.*)/, <$FH> : do { local $/ ; <$FH> };
}
sub getfile { local *ARGV ; @ARGV = shift ; wantarray ? map /(.*)/, <>
+ : do { local $/ ; <> } }
sub getfile {
my $filename = shift;
open my $FH, "<$filename" or die "Unable to open $filename: $!";
sysread $FH, my $contents, -s $FH;
return wantarray ? split m{$/}, $contents : $contents;
}
-
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.