Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • POD parsing (Score:2, Insightful)

    I think the best idea in those threads is ziggy's [] idea to use SAX as the canonical representation of POD. It was always the idea of the Orchard project to make orchard nodes the canonical representation of everything, but orchard nodes turned out to be too complex to install, so we ended up with hashes in PerlSAX2, which isn't so bad (albeit a bit memory expensive). Anyway, what I'm suggesting is you follow the PerlSAX2 node structure and event model, and we can then very easily write XML output or HTML out
    • I guess the only thing I don't get is the notion of being about to override tags for certain effects that will be placed within the actual POD itsself.

      My perspective is one of writing a module. I don't think about HTML, DocBook, or whatever final target when I am writing it. I am just thinking about what I need to express and trying to do it as consistently as possible! If the DocBook user wants to have certain tags exchanged for something else would this not be a feature of the pod2docbook?

      On the other

    • Re:POD parsing (Score:3, Informative)

      I don't envy you trying to sort this out :-)

      Me neither. :-)

      I've been wrestling with this in isolation for about a year now (I need to refill that bottle of daily tuit supplements), and Sean is really hitting the problem head-on. Kudos, Sean.

      What I've been fixated with is the idea of adding new linguistic constructs to Pod. The critical path here is first getting a better event-driven parser that simply parses Pod at the syntactic level without getting into the semantic meaning of Pod constructs.