While I do agree with virtualsue, I have a dissenting opinion. I am very new to perl, and programming itself. I can write shell scripts, but they tend to be limited. So I started writing my shell scripts in perl. It has taught me alot! The one most important thing I got out of it was this: I overcame my fear of perl, and it's structure, syntax, etc... I am making myself more comfortable with it each day I use it, and when I need the more advanced functions, I search on perlmonks and try to implement what I've seen. It's tough for me because the last time I wrote programs was about 14 years ago in high school, and that was in basic, and pascal on a TRS-80 (I loved my model 4). So while I agree that dfg2's script would best be written in #!/bin/ksh it might not be the best way to get into perl for a person just (re)starting programming.
-spartan
Very funny Scotty... Now PLEASE beam down my PANTS! | [reply]
[d/l] |
I am all for writing Perl programs - I do it myself all the
time.
It's just that the sequence of tasks in question is a perfect example of
something that can be done quickly & simply in shell, and
not so easily in Perl.
I'm not saying you're wrong, because you're not. It's easier to learn a
language if you have a motivation, something that you need
to accomplish. But in this case I think he'd be struggling
with it days after starting, when he'd have a tool he could
use that would make his life easier in a few minutes using
the shell language of his choice.
| [reply] |
I couldn't agree more.
-spartan
Very funny Scotty... Now PLEASE beam down my PANTS!
| [reply] |
| [reply] |
