There are modules that are intended for users that
are developers, and these may need very detailed technical
documentation, or even documentation about the implementation
of certain features.
In my personal experience with Perl, I'd say to these people:
read the code now, you will, anyway.
In general, I think POD syntax is the problem here, not the idea
of "inline" vs. "EOF" documentation. If POD syntax would
waste less screenspace, everybody would use "inline" POD
for implementation-level documentation.
Christian Lemburg
Brainbench MVP for Perl
http://www.brainbench.com