Today I had another look at POD parsing - there are a few small bugs in Pod::SAX's parsing of L<> items that are inherited from Pod::Parser. For example it won't correctly parse L<< A link with a file reference: F<foo/bar> >> because it treats the "/" as a L<> separator, then barfs because it sees the F< part and tries to treat it as a File reference, but can't find the end of it because the L<> parser swallowed it. All too horrible (and confusing to describe - so I don't expect readers to grok it any more than I do!). Basically what needs to be done is treat the text inside the L<> as the post-processed text equivalent after stripping all sequences inside. Unfortunately my parser doesn't provide me access to all that, and I'm not sure I'm up to the job of re-writing all the internals.
In short, I think it might be time to port Pod::SAX to using Pod::Simple instead of Pod::Parser. Though only because that might be the lesser of the two evils ;-)
"time" of course is relative. I don't exactly need that feature, and I'm sure there are very few users of Pod::SAX (aside from those who might use the AxKit Wiki) so it's very much non-urgent. Maybe I'll file myself a bug report in RT ;-)
Feel free to email me any questions you might have about some of the less well-documented parts of Pod::Simple::*.
I really meant to have all of Pod::Simple::* prettied up by now, but moving house across two timezones this past month caught me by surprise!
Re:Pod::Simple::SAX?
Matts on 2003-01-03T01:12:53
I think ultimately that'll be the best approach. All I lack now is time to JFDI;-)
Especially with my xmas hols almost over:-(
