On Thu, Mar 08, 2001 at 06:48:51PM -0500, Rob Napier wrote:
> But can Pod::Select then accept a ParseTree?
The function can't, but the module can. You can certainly
subclass it to do so and use all its methods (including the
ones it inherits from Pod::Parser) without having to call
parse_from_file. And the methods to invoke (or override)
in Pod::Parser can accept either a string *or* an object
(which can be a parse-tree, or something that contains it,
or something that simply implements the ParseTree interface).
> when I'm all done. The current Pod:: tools don't all seem to accept
> and return ParseTrees or pod strings, but maybe I'm overlooking it.
The Pod/InputObjects.pm file provides these parse-tree objects
and its brethren, and can accept them. And the Pod::Parser
methods like command() and interior_sequence() and such can
accept a Pod::Paragraph object (which I think implements the
ParseTree interface, I'd have to look at the code to refresh
my memory). And it lets you add nodes and evaluate them if
you like.
The TREE-BASED approach supported by Pod::Parser is admittedly
not as well documented as you probably would like, and thus isn't
the easiest to figure out how to use :-(
--
[EMAIL PROTECTED] | 847.632.7595 <[EMAIL PROTECTED]>
"And miles to go before I sleep." | Motorola ACE, ClearQuest/ClearCase
