#!/usr/bin/perl

use strict;
use warnings;
moose();
sub moose {
    my $filename = 'ter.pl';
    my $contents = do { local (*ARGV, $/) = [ $filename ]; <> };
    print $contents;
}

sub loose {
    my $filename = 'ter.pl';
    my $data= do { local( *ARGV, $/ );
    @ARGV= $filename; <> };
    print $data;

}
__END__
readline() on unopened filehandle ARGV at foo.pl line 8.
Use of uninitialized value in print at foo.pl line 9.
[download]

Oh, darn, it doesn't work in 5.6.x, only 5.8. Ah well, back to tye's version then...

I didn't know I had 5.8 installed :)

- Yes, I reinvent wheels.
- Spam: Visit eurotraQ.

Don't even think about it. If any of those even is consistently more efficient, the difference will be so small it is hardly going to matter. The key here is that it's a very concise way of doing what it does. In this case it is a oneliner, but in general, it doesn't matter how many lines an idiom takes (the Schwartzian Transform rarely fits in a single line, f.ex) - just that it is concise way of expressing a certain action. Don't confuse that with golfing: an idiom is not about saving keystrokes, it is about saving "brain cycles". The idea is that a) it is conveniently short so that people do use it and b) when you see it used in a snippet, you immediately know what it does just by the unique look of it.

It simplifies communication between the original programmer and the maintainer of his code.

Makeshifts last the longest.

OK! thanx. I agree that it is visually much more readable and I thought well, if it is faster also, cool. but i don't agree with you on one point: if it is even 1% faster, i'll take it for a script that has to process 100 000 files in a row.
Otherwise, for little scripts (read that process very little data)
I agree, I won't bother.

I don't like typing ARGV twice, but realise localizing *ARGV is necessary. Thanks for the pointer - I think I'm very fortunate to not have been bitten by this yet.