of course you are right, that's the punishment for not using strictures. :)
Just one nitpick: the benefit of parens here is technically not "list context" but precedence.
my has a higher precedence than comma, to allow other constructs like (my $a,my $b) =...
Maybe the perldoc should be clearer writing my (VARLIST) like in the doc of chomp (LIST)
> the number of source code lines does not equate directly into actual "code savings
Of course not, my intention here was readability.
It's right away obvious that both files are treated symmetrically, if the code is aligned in 2 dimensions.
Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!
In reply to Re^5: writing two files (different in length) to one output
by LanX
in thread writing two files (different in length) to one output
by ic23oluk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |