I highly recommend getting in the habit of making your programs filters. Happily, Perl has a great way to do this:
while (<>) {
# do stuff on $_ line by line
}
This will either take direct STDIN (run the program, it sits there, you enter lines of text until you hit ctrl-D), or take a list of filenames on the command line and process their contents as STDIN. Because this idiom doesn't use any textual identifier (like ARGV or STDIN), and because it's a difficult concept for a newbie to describe or search for (or even to conceive of), it's often something people don't pick up on early. I'm going to go on a limb and counsel a novitate to "just do it," and adapt your intentions to fit this idiom.
It's not exactly what you described -- the others' @ARGV solutions are for that -- but if you can alter your requirement slightly, writing programs as filters has a lot of benefits. See The Art of Unix Programming for why.
-
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.
|