Barrie Slaymaker writes:
> I was proposing Pod::StdParser as a more low-level approach that
> generated callbacks:
Hmmn - not sure what you mean by "generate" callbacks.
Pod::Parser already provides for registration and invocation
of callbacks in a number of ways, same which use inheritance
and some which use code-refs. I had in mind to have all of
them use code-refs eventually (resolving all inherited method
calls to code-refs with an initial preprocessing step).
So that part can genuinely go into Pod::Parser, and I have
some initial code if anyone wants to run with it. Pod::Parser
can also be used to simply spit out parse-trees and each
*paragraph* and sequence in the parse-tree can either be a
Pod::* object from Pod/InputObjects.pm, *or* you can make it
be your own object (which can be a callback, or something with
a predefined method) if you like.
So I think much of that is already there. And I think eliminating
method calls by precomputing them beforehand would be a big
speedup (and we all know performance is a big issue with the
current implementation of Pod::Parser)
--
Brad Appleton <[EMAIL PROTECTED]> http://www.bradapp.net/
"And miles to go before I sleep." -- Robert Frost
