I know there must be a /simple/ way to make a Pod::ParseTree parse tree,
but I'm not seeing it. In the 5,000 words of Pod::Parser's POD, there's a
long tractatus about ways to make subclasses that elaborate (inarborate?) a
Pod::ParseTree. But in the end, it sort of handwaves off to
Pod::InputObjects -- whose documentation is, to put it diplomatically, too
much and yet not enough.
So, how do I get a parse tree, with the Pod::Parser modules, out of the
box? In short, I'm looking for the short Pod::ParseTree incantation that
corresponds to what I do in HTML::TreeBuilder with:
use HTML::TreeBuilder;
(my $tree = HTML::TreeBuilder->new)->parse_file('thing.html');
$tree->dump;
$tree->delete;
Maybe I've just not joined the higher primates and come down out of the
trees, but I think doctrees are they way to go for all but ad-hoc or
partial processing -- because you can poke and prod and scan and rearrange
and dump a tree, whereas events just come at you in whatever order they get
fired in.
--
Sean M. Burke [EMAIL PROTECTED] http://www.spinn.net/~sburke/
