>OK, there's one non-incremental idea: documentation that you can write
>in one place and display in some completely different order. (Shades of
>literate programming!) And although there are good reasons for keeping
>the docs in the same file as the code, there are equal but opposite
>reasons to keep it separate (if it's all piled up at the end of the file
>anyway). What gets presented to the user as "one page" could be bits
>and pieces from all over the place.
Literate Programming handles reordering by allowing you to specify a
hirearchical number as part of each doc piece. This could be easily a
dded to POD. Something like:
=(1.2.1) begin ...
just default any unspecified values to incrementing the last one.
A simple POD processor could just ignore them and a fancy one could
use them to reorder the section accordingly.
--
Mark Biggar
[EMAIL PROTECTED]
