Re^2: How-To on Perl one-liners

in reply to Re: How-To on Perl one-liners
in thread How-To on Perl one-liners

Absolutely true, and thank you for the code. However, I work on several systems, all of which have Perl, but not all of which have a consistent or sane shell. I believe the relevant quote is, "It is easier to port a shell than a shell script." My thinking in asking the question is, if I grok Perl one-liners, I don't need shell scripting nearly as much.

Comment on Re^2: How-To on Perl one-liners

Replies are listed 'Best First'.
Re^3: How-To on Perl one-liners by Mugatu (Monk) on Apr 04, 2005 at 16:54 UTC
if I grok Perl one-liners, I don't need shell scripting nearly as much Indeed, but with oneliners, you still need to know the shell fairly well. I'm not implying you don't, but I'm just trying to make the point. There are many shell gotchas involved when writing oneliners. Most common are quoting and glob expansion (or expansion in general) woes. Also, it's often more natural to use a perl oneliner as part of the pipeline, rather than the entire thing. This requires knowing the shells you're working with. There's really no [reasonably convenient] way of avoiding it. :-)	[reply]

Replies are listed 'Best First'.

Re^3: How-To on Perl one-liners
by Mugatu (Monk) on Apr 04, 2005 at 16:54 UTC

if I grok Perl one-liners, I don't need shell scripting nearly as much

Indeed, but with oneliners, you still need to know the shell fairly well. I'm not implying you don't, but I'm just trying to make the point. There are many shell gotchas involved when writing oneliners. Most common are quoting and glob expansion (or expansion in general) woes. Also, it's often more natural to use a perl oneliner as part of the pipeline, rather than the entire thing. This requires knowing the shells you're working with. There's really no [reasonably convenient] way of avoiding it. :-)

[reply]

In Section Seekers of Perl Wisdom