++ed by:
1 non-PAUSE user
Author image Mark Overmeer
and 1 contributors


OODoc::Format::Pod - Produce POD pages from the doc tree


   is a OODoc::Format
   is a OODoc::Object

 OODoc::Format::Pod is extended by


 my $doc = OODoc->new(...);
   ( 'pod'
   , format_options => [show_examples => 'NO']
   , append         => "extra text\n"


Create manual pages in the POD syntax. POD is the standard document description syntax for Perl. POD can be translated to many different operating system specific manual systems, like the Unix man system.





Inheritance knowledge







Page generation

$obj->cleanup(MANUAL, STRING)

$obj->cleanupPOD(IN, OUT)

    The POD is produced in the specified IN filename, but may contain some garbage, especially a lot of superfluous blanks lines. Because it is quite complex to track double blank lines in the production process, we make an extra pass over the POD to remove it afterwards. Other clean-up activities may be implemented later.


     Option        --Defined in     --Default
     append                           ''
     format_options  OODoc::Format    []
     manual          OODoc::Format    <required>
     project         OODoc::Format    <required>
     template        OODoc::Format    undef

    . append => STRING|CODE

    . format_options => ARRAY

    . manual => MANUAL

    . project => STRING

    . template => LOCATION



    The OPTIONS are a collection of all options available to show* methods. They are completed with the defaults set by createManual(format_options).

     append  ''
     manual  <required>
     output  <required>

    . append => STRING|CODE

      Used after each manual page has been formatting according to the standard rules. When a STRING is specified, it will be appended to the manual page. When a CODE reference is given, that function is called with all the options that showChapter() usually gets.

      Using append is one of the alternatives to create the correct Reference, Copyrights, etc chapters at the end of each manual page. See "Configuring".

    . manual => MANUAL

    . output => FILE

$obj->link(MANUAL, OBJECT, [TEXT])

    Create the text for a link which refers to the OBJECT. The link will be shown somewhere in the MANUAL. The TEXT will be displayed is stead of the link path, when specified.


    There is (AFAIK) no way to get the standard podlators code to remove all markup from a string: to simplify a string. On the other hand, you are not allowed to put markup in a verbatim block, but we do have that. So: we have to clean the strings ourselves.


$obj->showChapterIndex(FILE, CHAPTER, INDENT)





$obj->showOptionalChapter(NAME, OPTIONS)


$obj->showRequiredChapter(NAME, OPTIONS)









     ARRAY   <required>
     header  <required>
     output  <required>
     widths  undef


      An array of arrays, each describing a row for the output. The first row is the header.

    . header => ARRAY

    . output => FILE

    . widths => ARRAY

Commonly used functions





Manual Repository









Probably, the output which is produced by the POD formatter is only a bit in the direction of your own ideas, but not quite what you like. Therefore, there are a few ways to adapt the output.

Configuring with format options

createManual(format_options) or OODoc::create(format_options) can be used with a list of formatting options which are passed to showChapter(). This will help you to produce pages which have pre-planned changes in layout.

example: format options

 use OODoc;
 my $doc = OODoc->new(...);
 $doc->create(pod =>
    format_options => [ show_subs_index     => 'NAMES'
                      , show_inherited_subs => 'NO'
                      , show_described_subs => 'USE'
                      , show_option_table   => 'NO'

Configuring by appending

By default, the last chapters are not filled in: the REFERENCES and COPYRIGHTS chapters are very personal. You can fill these in by extending the POD generator, as described in the next section, or take a very simple approach simply using createManual(append).

example: appending text to a page

 use OODoc;
 my $doc = OODoc->new(...);
 $doc->create('pod', append => <<'TEXT');


Configuring via extension

OODoc is an object oriented module, which means that you can extend the functionality of a class by creating a new class. This provides an easy way to add, change or remove chapters from the produced manual pages.

example: remove chapter inheritance

 $doc->create('MyPod', format_options => [...]);

 package MyPod;
 use base 'OODoc::Format::Pod';
 sub chapterInheritance(@) {shift};

The MyPod package is extending the standard POD generator, by overruling the default behavior of chapterInheritance() by producing nothing.

example: changing the chapter's output

 $doc->create('MyPod', format_options => [...]);

 package MyPod;
 use base 'OODoc::Format::Pod';

 sub chapterCopyrights(@)
 {   my ($self, %args) = @_;
     my $manual = $args{manual} or confess;
     my $output = $args{output} or confess;

     $output->print("\n=head2 COPYRIGHTS\n");
     $output->print($manual->name =~ m/abc/ ? <<'FREE' : <<'COMMERICIAL');
This package can be used free of charge, as Perl itself.
This package will cost you money.  Register if you want to use it.


example: adding to a chapter's output

 $doc->create('MyPod', format_options => [...]);

 package MyPod;
 use base 'OODoc::Format::Pod';

 sub chapterDiagnostics(@)
 {   my ($self, %args) = @_;

     my $output  = $args{output} or confess;
     my $manual  = $args{manual} or confess;
     my @extends = $manual->superClasses;

     $output->print(\nSee also the diagnostics is @extends.\n");

Configuring with Template::Magic

When using 'pod2' in stead of 'pod' when OODoc::create() is called, the OODoc::Format::Pod2 will be used. It's nearly a drop-in replacement by its default behavior. When you specify your own template file, every thing can be made.

See the manual page of Template::Magic. You have to install Bundle::Template::Magic to get it to work.

example: formatting with template

 use OODoc;
 my $doc = OODoc->new(...);
 $doc->create(pod2, template => '/some/file',
    format_options => [ show_subs_index     => 'NAMES'
                      , show_option_table   => 'NO'

example: format options within template

The template van look like this:

 {chapter NAME}
 some extra text
 {chapter OVERLOADED}
 {chapter METHODS show_option_table NO}

The formatting options can be added, however the syntax is quite sensitive: not quotes, comma's and exactly one blank between the strings.


Error: cannot read prelimary pod from $infn: $!

Error: cannot write final pod to $outfn: $!

Error: cannot write pod manual at $manfile: $!

Error: formatter does not know the version.

Error: formatter has no project name.

    A formatter was created without a name specified for the project at hand. This should be passed with new(project).

Error: manual definition requires manual object

Warning: missing required chapter $name in $manual

Error: no directory to put pod manual for $name in

Error: no package name for pod production

Error: no package name for pod production

Error: no working directory specified.

    The formatter has to know where the output can be written. This directory must be provided via new(workdir), but was not specified.

Warning: unknown subroutine type $type for $name in $manual


This module is part of OODoc distribution version 1.04, built on June 12, 2008. Website: http://perl.overmeer.net/oodoc/


Copyrights 2003-2008 by Mark Overmeer. For other contributors see ChangeLog.

This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See http://www.perl.com/perl/misc/Artistic.html