On Wed, Aug 02, 2000 at 03:52:15PM -0400, Barrie Slaymaker wrote:
> =head1 IMPLEMENTATION
>
> The C<=also> command is implemented in Pod::Parser in a process
> called "=also mangling".
Why is this handled in Pod::Parser when =for and =begin/=end
aren't presently handled or known to Pod::Parser?? All Pod::Parser
knows is that it saw a paragraph beginning with /^=(\w+)/ and that
the client/caller needs to look at $1 and the stuff that came
after it and let the caller decide how (if at all) they will
respond to that piece of input. Pod::Parser knows it is some
command; its had no idea which command it is or what it means
(this is deliberate).
Pod::Parser is not supposed to know about any =xxx commands
other than =cut. Anything else, it knows only the syntax
(e.g. /^=\w+/) and cannot assume it knows which =xxx keywords
are valid commands and which ones are not (because it has to
allow specialized scripts to (re)create or extend their own
pod-like languages).
I'd rather see this implemented as something in Pod:::ParseUtils
that all other POD xlators can use, rather than inside Pod::Parser
where it would break existing code/scripts (even if those aren't
part of the core Perl distribution).
--
Brad Appleton <[EMAIL PROTECTED]> http://www.bradapp.net/
"And miles to go before I sleep." -- Robert Frost
