On Fri, Aug 04, 2000 at 05:11:31PM -0400, Barrie Slaymaker wrote:
> Brad doesn't want it to go in to the main Pod::Parser, I
> don't want to have every POD translator maintainer/author
> have to implement =also functionality.
Those two aren't diametrically opposed you know. The main error
in the above is referring to Pod::Parser as "the main" parser
rather than "the base" parser. Pod::Parser is a *base* parser.
There is no *main* parser right now. Everyone keeps assuming
that its Pod::Parser, but they're incorrect.
Have someone actually write the main parser, Then put the
=also functionality there. Marek is correct in that much
of the main parser would resemble Pod::Checker.
I've suggested calling the main parser Pod::Translator or
Pod::Compiler before. I've even suggested renaming Pod::Parser
to Pod::Lexer and call the main parser Pod::Parser (once it
is written).
But until that happens, let us please not make the confusion
worse by calling Pod::Parser the *main* parser, for it clearly
does not do all the things one would like a main parser
to do (and was never intended to). It was only ever a *base*
parser, to be reused for all things Pod-like (including, but
by no means limited to, translating perlpod-specified format
into some other output format).
The self->cmd_name() functionality you describe is something
I've intended to be part of Pod::Parser for quite a while. I've
even had it designed, prototyped, and working for two years
now. I just wasn't happy with the interface. If someone wants
to take what I have and see what they can do with it, please
let me know and I'll send you the code.
Cheers!
--
Brad Appleton <[EMAIL PROTECTED]> http://www.bradapp.net/
"And miles to go before I sleep." -- Robert Frost
