why wouldn't you assume he'd know basic perl? | [reply] |
We can't all be geniuses like you, Anonymous.
| [reply] |
Mainly because it's *not* basic Perl. It's a subtle effect that isn't obvious. If the OP included the ampersands without commenting, it would be reasonable for a maintainer to remove them, not knowing the effect they have on speed. And as you are fond of pointing out, not everyone who programs is a good programmer, right?
| [reply] |
It's a subtle effect that isn't obvious.
well, it's documented in the beginning of perlsub.pod. i want to program assuming
my co-workers/successors have at least read the common perldoc-pages. i don't
want to comment things that are already documented in the documentation for perl
itself.
what i *would* docunment in a case like this is *why* i do this. so instead of
saying
&foo; # give current @_ to foo.
i'd say
&foo; # foo needs @_ because ...
then any programmer stumbling over this code would know why or have to read perlsub.
| [reply]
[d/l]
[select] |
