- arbitrary subroutine sets come into play at so high a level of abstraction that only very specific situations can imagineably need them. Multiple filehandles are an everyday occurrence. Unless you're the kind of programmer that still uses global variables for everything, it is necessary to lexically rather than bareword declare filehandles to manage their scope.
- the bareword is just a syntax. There might be rare occasions where specifying a filehandle as a bareword is needed. What is possible with a language does not mean that anything allowed is good practice. For example, proper indentation is good practice. Python enforces it Perl doesn't - this is a feature of Perl, not a licence to write unreadable code.
- Only the writer knows if his jerking of a the knee is a kneejerk reaction or a carefully considered jerking of the knee. You don't have a clue.
- Just because there is more than one way to do something doesn't mean all ways have equal merit all the time.
- You have a lot to learn!
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.