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!
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
