On Dec 19, Ryan Guy said:
>kept doing that for a whole program.) Anyways what I am getting at is that
>the compiler optimizer works in tune with good coding practicing. It trips
>and falls when you try to cram all that shit on one-line (with a few
>exceptions). I always hear all this hype about how great one liners are,
>but it is all just a myth.
I'm not sure I understand your gripe. One-liners are no different from
other programs.
perl -pi -e 's/foo/bar/g' ...
is no different from
#!/usr/bin/perl -pi
s/foo/bar/g;
nor from
#!/usr/bin/perl -p
BEGIN { $^I = "" }
s/foo/bar/g;
It's just more convenient (for me) to have a one-liner. It's just a
matter of convenience. Many people ignore the command-line options to
Perl when they're not writing one-liners.
--
Jeff "japhy" Pinyan [EMAIL PROTECTED] http://www.pobox.com/~japhy/
RPI Acacia brother #734 http://www.perlmonks.org/ http://www.cpan.org/
** Look for "Regular Expressions in Perl" published by Manning, in 2002 **
<stu> what does y/// stand for? <tenderpuss> why, yansliterate of course.
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
