Hmmm, I like the open my $INFILE ... construct. I'll have to remember it since I use the 
open INFILE,"<","testfile.txt" or die "Could not open file:$!";
$fh = \*INFILE;

[download]
code a lot.

On a personal note, I have never felt comfortable with the arrow op. It may just be lack of use although I have been using it more lately. I do agree with you about scalability. I generally end up using the arrow op on more complex structures - although I do have a $$$cfg{infile} line in this same program ;o) - Still, it does look cleaner here...

Thanks for the suggestions.

PJ
unspoken but ever present -- use strict; use warnings; use diagnostics; (if needed)

In reply to Re^2: Indirect Referencing by periapt
in thread Indirect Referencing by periapt

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.