Barrie Slaymaker <[EMAIL PROTECTED]> writes:
> Agreed, especially if volunteers can be found to port existing Pod::Foo
> converters to use this new Pod::StdParser (or whatever). I like the way
> that Pod::Text does $self->cmd_foo(...) dispatch, perhaps
(As an aside, please do bear in mind that Pod::Text and Pod::Man have an
active maintainer, namely me, although I realize that I don't have a
regular allotment of time to spend on them and therefore tend to do
updates in batches every three or six months.)
> - moving $self->cmd_foo() dispatch to Pod::Parser,
> - allows =for/=begin...=end filtering
This is certainly doable (although I question whether Pod::Parser is the
right place for it), but it's also worth bearing in mind that you're
talking about a grand total of about twenty lines of code here, tops.
Very stable code, too. There's something to be said for each translator
just doing this very small amount of work itself so that it has control
over it.
> - creating a Pod::StdParser that
> - knows about well-formedness,
What well-formedness in particular are you thinking of? This is a serious
question; in working with translators, I've found that this isn't nearly
as large of a problem as one might think. There really isn't much about
POD that *can* be ill-formed. Notice that there are precisely four carps
in the entirety of Pod::Text (unrecognized interior sequence, unrecognized
E<> escape, =back without =over, and =item without a tag).
> - implements C<=also>, and
See other comments.
> - provides some status attributes & methods to allow context to be
> queried, like if you're in an =for/=begin...=end region
I just use instance variables for this in my translators, and that works
fine. Again, this is a very small amount of code.
> - porting Pod::Text, some Pod::Html, etc., to use Pod::StdParser would
> be good.
So far, I've honestly not seen any reason at all to do this.
> Subclasses to support added commands would be able to define new members
> for each command they add: =bar needs a sub cmd_bar() {}.
Again, very little code needed for this.
I am interested in continuting to maintain the POD translators that I
wrote, and if this is the way that we want the wind to shift, I'll try to
help. But so far, again, I'm unenthused.
--
Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
