Not sure it has to do with prerogatives. Clearly, keeping the comments at the function head is the simplest to _maintain_. But for the aforementioned reasons, having a long comment about how a function works _obscures_ the code near it and makes it hard to _read_. In addition, any comments not immediately helpful to the maintainer make the _code_ harder to maintain. Now this normally isn't a problem because programmers don't actually write documentation (see most perl modules for evidence). Thus, having a small amount of documentation for each function isn't a big deal. The problem comes when you have _more_ documentation than the cursory few lines. Obviously it's great if you can keep your comments brief, but what if more explanation is needed?
Clearly someone in charge agrees with me as the existence of "__END__" demonstrates.
In reply to Re^2: POD using __END__ with function comments
by zerohero
in thread POD using __END__ with function comments
by zerohero
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |