I am midway thru adapting Pod::Man to Pod::Simple::Man -- that is,
replicating the Pod/Man.pm logic under a different parser framework.
It's going pretty ideally -- that is, about the only code that is changing
is the code that interfaces with the parser libraries (was Pod::Parser, is
Pod::Simple); and I expect that in the end I'll be able to "verify the
correctness" (as was said in times of Lisp and yore) of the resulting
module with a bunch of regression tests against a pile of output from the
current Pod::Man.
Undergirding it all like a TITANIUM JOCKSTRAP, there is some code I've
written that could not even remotely be called a general Pod::Parser
emulator, but which is form-fitted for how Pod::Man's manly bulges have
grown so used to the contours of Pod::Parser.
The amount of *roff-specific code that I've had to tinker with so far is
roughly zero, which is as it should be, since I mean the resulting code to
be at least as intelligible to the current *roff-literate Pod::Man people
as the current Pod::Man itself is. I will be happy if this change of
parsing libraries causes as little disruption as possible.
I will now stop talking about jockstraps, barring further
requests. Thongs, however, may be a recurring theme, and sportsbras may
make an appearance, except in reference to any modules with "man" in their
name. Trusses will be reserved for hernia cases, and harnesses for modules
that require spanking.
--
Sean M. Burke http://search.cpan.org/~sburke/
