Well, I would make coding standards for good programmers,
and from a good programmer, I would assume he/she knows
the language. Non-perl programmers shouldn't program Perl.
And as a manager, or tech-lead, I wouldn't allow non-Perl
programmers to touch Perl code.
Perhaps rule 0 should be: "People who can't program in Perl
are not allowed to touch the code".
$_ is one of the most basic things in Perl. If
you have problems with the readability of $_,
you shouldn't call yourself a Perl programmer.
Abigail | [reply]
[d/l]
[select] |
I support using $_, but you should perhaps implement a standard/guideline in the form of 'Localize $_ in all user created subs', as something like the following:
sub foo{my $blah=shift; $_=substr $blah,0,1; /foo/;}
Which looks fairly innocuous in the use of $_ to avoid more temporary vars (It's not an extremely good example, but it serves), but then you do something likemap{foo($_->[0]);$_;} which can return wildly different results then you expected, and lead to many.. interesting.. bugs. | [reply]
[d/l]
[select] |
Wow, that really localizes $_ ? To me, it looks more like a straight assignment to $_. I would've expected something like:
sub foo { local $_ = shift; /foo/; }
blyman
:wq | [reply]
[d/l] |