demerphq has asked for the wisdom of the Perl Monks concerning the following question:

The documentation for 5.6.1 perlpod explicitly mentions only =head1 and =head2, the documentation in 5.8.2 and 5.8.6 mention =head1 through =head4.

Does this mean that using =head3 and =head4 isn't going to work on a bunch of perls?

Whats the best approach with this? Avoid =head3 and =head4?

Shame on you folks who thought this was going to be about something other than perl. :-)

---
$world=~s/war/peace/g

Replies are listed 'Best First'.
Re: Getting good =head
by diotalevi (Canon) on Jan 03, 2006 at 20:42 UTC

    =head3 and above break pod tools on older perls. It's incredibly annoying to have to edit another person's module just to get it to install and the only backwards compatibility issue is the broken pod. You should probably only use those features if you've already commited other things which aren't backwards compatible.

    I don't remember what versions I using. You'll need to cross-reference at what point in perl =head3+ became available.

    ⠤⠤ ⠙⠊⠕⠞⠁⠇⠑⠧⠊

Re: Getting good =head
by ptum (Priest) on Jan 03, 2006 at 19:56 UTC

    I've never really needed anything deeper than =head2 -- I tend to use =item below that point. I note that Pod::Coverage (and probably other Pod:: modules) will handle =head\d with no trouble.


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

      I mostly want it because in Pod::HTML and similar things it builds the index from the =head entries. I find two layers is often a bit flat.

      ---
      $world=~s/war/peace/g

        If they can upgrade Pod::Html, it will work