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.