Hi,
for this I have written Pod::Compiler, which is on CPAN. I hope its
documentation is not too clumsy. It may have some bugs, but the structure
should be complete. I though of it as a basis for converters into the more
complex formats like HTML, FrameMaker, PDF etc. that have hyperlinks.
Such a converter would use the Pod::Compiler as a basis and provide
additional methods, e.g. "as_html" to all the classes of Pod::Objects (I
know this is not clean OOP, but IMHO it is simple and efficient). I was
planning to write a Pod::HTML based on the compiler and later a Pod::MIF
(FrameMaker).
There is also Pod::Tree, which does a similar thing. However I based my
work on Pod::Parser which to me is the standard frontend to the POD
format.
Cheers,
Marek
On Fri, 3 Aug 2001, Sean M. Burke wrote:
SMB>I know there must be a /simple/ way to make a Pod::ParseTree parse tree,
SMB>but I'm not seeing it. In the 5,000 words of Pod::Parser's POD, there's a
SMB>long tractatus about ways to make subclasses that elaborate (inarborate?) a
SMB>Pod::ParseTree. But in the end, it sort of handwaves off to
SMB>Pod::InputObjects -- whose documentation is, to put it diplomatically, too
SMB>much and yet not enough.
SMB>
SMB>So, how do I get a parse tree, with the Pod::Parser modules, out of the
SMB>box? In short, I'm looking for the short Pod::ParseTree incantation that
SMB>corresponds to what I do in HTML::TreeBuilder with:
SMB> use HTML::TreeBuilder;
SMB> (my $tree = HTML::TreeBuilder->new)->parse_file('thing.html');
SMB> $tree->dump;
SMB> $tree->delete;
SMB>
SMB>Maybe I've just not joined the higher primates and come down out of the
SMB>trees, but I think doctrees are they way to go for all but ad-hoc or
SMB>partial processing -- because you can poke and prod and scan and rearrange
SMB>and dump a tree, whereas events just come at you in whatever order they get
SMB>fired in.
SMB>
SMB>
SMB>--
SMB>Sean M. Burke [EMAIL PROTECTED] http://www.spinn.net/~sburke/
SMB>
