NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
brian_d_foy (44)
Journal of brian_d_foy (44)
Saturday May 08, 2004
03:38 PM
Let the script figure it out
Today's exercise: let the program, which is really a module with a run() mehtod, figure out what to do based on how I call it. Not using semicolons is just a bonus feature.
sub run
{
$_[0]->new->${
\(do {
if( defined $ENV{ REQUEST_METHOD } ) { 'as_html' }
elsif( -t STDIN ) { 'as_text' }
else { 'as_file' }
})
}
}
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
Full
Abbreviated
Hidden
Loading... please wait.
--Larry Wall in stab.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
file (Score:2)
Re:file (Score:2)
STDIN or STDOUT (Score:2)
-t STDIN a bit of an odd criterium to decide what kind of output to get. I often run programs from the command line, that doesn't mean I want interactive output. Or on the contrary, it's not because my source comes from a file, that it means I want it to go to a file.In short, I'd rather use-t STDOUTto decide on kind of output instead. I imagine thatlsbehaves this way.If you want to override it, there's always command line switches.