in reply to A common piece of POD

Heh. Maybe instead of propagating a duplicate bit of POD, you should pull the common 'dirty hack' code out of each module and put it into a common Utilities module. Then you could document it once (or even fix it once) and use it in all your other modules. Of course, this would require you to edit each of the existing modules, which may be what you're trying to avoid doing. :)

It doesn't really answer your question, but that is what I would do.

Alternatively you could use an embedded hyperlink (L<name>) to point at your external POD.


No good deed goes unpunished. -- (attributed to) Oscar Wilde

Replies are listed 'Best First'.
Re^2: A common piece of POD
by blazar (Canon) on Jan 20, 2006 at 14:21 UTC

    Unfortunately it is not possible to factor out the "dirty hack" because it is only "morally" the same (abusing a method for something it's not really meant for) but is actually different in practice from module to module.