That's right... specifically, it depends on what is currently in @ARGV
(if there's anything in @ARGV
, the contents are treated as file names, and the files are magically opened and read from... if @ARGV
is empty, it'll read from STDIN).
If the intent is to read from STDIN, then do so, explicitly, by <STDIN>. If the intent is to process files, generically, either named files or files piped through, then use <>. In the case of the original post, which seems to be (maybe) testing some external code and trying to sandbox it, somewhat, it might just be a good idea to localize @ARGV (that is, to extend the sandbox beyond just STDIN and STDOUT (why isn't he also tieing STDERR, then, though?) to include the command line).
Not an editor command: Wq
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||