Lines Matching refs:parse
66 ## Create a parser object and have it parse file whose name was
152 A I<parse-option> is simply a named option of B<Pod::Parser> with a
155 or unsetting one or more I<parse-options> using the B<parseopts()> method.
156 The set of currently accepted parse-options is as follows:
196 for the setting and unsetting of parse-options.
607 but before trying to further parse or interpret them. After
656 B<parse_text()> will parse the given text into a parse-tree of "nodes."
657 and interior-sequences. Each "node" in the parse tree is either a
659 parse-tree of type B<Pod::ParseTree>. Please see L<Pod::InputObjects>
663 to customize certain aspects of the parse-tree that is created and
670 Normally, the parse-tree returned by B<parse_text()> will contain an
692 Normally, the parse-tree returned by B<parse_text()> will contain a
712 node in the parse-tree (usually an interior-sequence object or else the
713 top-level node of the parse-tree).
717 Rather than returning a C<Pod::ParseTree>, pass the parse-tree as an
719 object) and return the result instead of the parse-tree object.
730 is a reference to the parse-tree object.
773 ## stack. It's really a parse-tree, not a sequence; but it implements
775 ## and strings we parse. Thus, by the end of our parsing, it should be
828 ## Append result to its parent in current parse tree
869 ## Return the resulting parse-tree
921 local *myOpts = ($myData{_PARSEOPTS} ||= {}); ## get parse-options
1021 wrapper object could be used to parse PODs from a single string or an
1027 encountered it will invoke a method to parse the given paragraph.
1049 local *myOpts = ($myData{_PARSEOPTS} ||= {}); ## get parse-options
1224 ## have to parse the input and close the handles when we're finished.
1306 name of a parse-option and returns its corresponding value if it exists
1314 key/value pairs and the specified parse-option names are set to the
1315 given values. Any unspecified parse-options are unaffected.
1321 reset the existing parse-options, all previous parse-option values
1328 parse-option currently recognized.
1412 B<parse_from_file()> or B<parse_from_filehandle()> to parse a new input
1596 may be desirable to instead create a parse-tree using the B<parse_text()>
1605 several objects that may all be used interchangeably as parse-trees. The
1607 interface and functionality that all things trying to be a POD parse-tree
1609 text-string, or a reference to another parse-tree. Each B<Pod::Paragraph>
1611 parse-tree interface.
1614 returns a parse-tree that contains one or more children, each of which
1618 returned result. These callbacks can be used to create a parse-tree
1619 with custom-made objects (which may or may not support the parse-tree
1622 If you wish to turn an entire POD document into a parse-tree, that process
1628 parse-tree. So for each of those paragraph-callback methods, simply call
1630 parse-tree to assign to the given paragraph object.
1632 That gives you a parse-tree for each paragraph - so now all you need is
1681 interface for all parse-tree nodes. The result would look something like:
1689 $self->{'-ptree'} = new Pod::ParseTree; ## initialize parse-tree
1693 ## convenience method to get/set the parse-tree for the entire POD
1726 Now you have the entire POD document as one great big parse-tree. You
1735 custom node-types in the parse-tree) and add some kind of B<emit()>
1747 command paragraphs, parse-trees, and interior-sequences.