There is an alternative approach that I have used in just such a situation that I think is worth considering.

You can place all your POD in a single file for documentation/admin and then have a script that creates the individual PODs for each script either as .POD or rewriting the original file.

This is a bit of a kludge and only really works with small groups of closely related files where updating one will directly impact another (ie if A requires B then B doc may say required by A). It is also nice for due diligence when you can extract an overview that maps to the spec and show how it maps all the way down to the code level.

You can also use this approach when starting a project if you have a clear functional/technical specification to auto create documented stubs for your packages or scripts.

Hope this is not too confused
UnderMine

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.