Author image Zahatski Aliaksandr
and 1 contributors


Perl6::Pod::Directive::use - handle =use directive


Load the corresponding Perldoc module:

    =use Test::Tag
    =for Tag
    text data

Define own formatting code:

    =use Perldoc::TT
    =config TT<>  :allow<E>
    head1 Overview of the M<TT: $CLASSNAME > class


Perldoc provides a mechanism by which you can extend the syntax, semantics, or content of your documentation: the =use directive.

Specifying a =use causes a Perldoc processor to load the corresponding Perldoc module at that point, or to throw an exception if it cannot.

Such modules can specify additional content that should be included in the document. Alternatively, they can register classes that handle new types of block directives or formatting codes.

Note that a module loaded via a =use statement can affect the content or the interpretation of subsequent blocks, but not the initial parsing of those blocks. Any new block types must still conform to the general syntax described in this document. Typically, a module will change the way that renderers parse the contents of specific blocks.

A =use directive may be specified with either a module name or a URI:

    =                 OPTIONAL EXTRA CONFIG DATA
    =use URI

If a URI is given, the specified file is treated as a source of Pod to be included in the document. Any Pod blocks are parsed out of the contents of the =use'd file, and added to the main file's Pod representation at that point.

If a module name is specified with any prefix except pod:, or without a prefix at all, then the corresponding .pm file (or another language's equivalent code module) is searched for in the appropriate module library path. If found, the code module require'd into the Pod parser (usually to add a class implementing a particular Pod extension). If no such code module is found, a suitable .pod file is searched for instead, the contents parsed as Pod, and the resulting block objects inserted into the main file's representation

Any options that are specified after the module name:

    =use Perldoc::Plugin::Image  :Jpeg  prefix=>''

are passed to the internal require that loads the corresponding module.

Collectively these alternatives allow you to create standard documentation inserts or stylesheets, to include Pod extracted from other code files, or to specify new types of documentation blocks and formatting codes:

  • To create a standard Pod insertion or stylesheet, create a .pod file and install it in your documentation path. Load it with either:

              =use Pod::Insertion::Name


              =use pod:Pod::Insertion::Name


              =use file:/full/path/spec/Pod/Insertion/Name.pod

    or even:

  • To insert the Pod from a .pm file (for example, to have your class documentation include documentation from a base class):

              =use pod:Some::Other::Module
  • To implement a new Pod block type or formatting code, create a .pm file and load it with either:

              =use New::Perldoc::Subclass

    or (more explicitly):

              =use perl6:New::Perldoc::Subclass
  • To create a module that inserts Pod and also require's a parser extension, install a .pod file that contains a nested =use that imports the necessary plug-in code. Then load the Pod file as above.

    A typical example would be a Perldoc extension that also needs to specify some preconfiguration:

              =use Hybrid::Content::Plus::Extension

    Then, in the file some_perl_doc_dir/Hybrid/Content/Plus/Extension.pod:

              =begin code :allow<R>
              =comment This file sets some config and also enables the Graph block
              =config Graph :formatted< B >
              =use perl6:Perldoc::Plugin::Graph-(*)-cpan:MEGAGIGA
              =end code

    Note that =use is a fundamental Perldoc directive, like =begin or =encoding, so there is no paragraph or delimited form of =use.


Perl6::Pod handle exended syntax:

    =                 OPTIONAL EXTRA CONFIG DATA

    =                 OPTIONAL EXTRA CONFIG DATA

Fo example:

    =comment Overwrite default class for standart formatting code
    =use Perldoc::TT B<>

    =comment Define custom BlockNames
    =use Perldoc::TT Alias1
    =use Perldoc::TT Alias2

Perl6::Pod also handle ${PERL6POD} variable in package namespace. It used for evalute Pod chunk for loaded Module.

For package contains variable $PERL6POD:

    package UserDefined::Lib;
    use strict;
    use warnings;
    our $PERL6POD = <<POD;
    =begin pod
    =use UserDefined::Module
    =use UserDefined::Image
    =end pod

We can evalute Pod in the Pod file:

    =begin pod
    =comment Evalute $PERL6POD
    =use UserDefined::Lib
    =comment Now will use =Image  block
    =end pod

SEE ALSO, Perldoc Pod to HTML converter:, Perl6::Pod::Lib


Zahatski Aliaksandr, <>


Copyright (C) 2009-2015 by Zahatski Aliaksandr

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.8 or, at your option, any later version of Perl 5 you may have available.