> the same question. Also, interested developers should look at the .t > files, which contain hundreds of examples of Pod input and the XML output > that it should produce.
Cool! I'm so glad we finally have full use of regression tests for POD input and output. > In writing Pod::Simple, I have thought mostly of the tasks of writing Pod > formatters. I would like to hear from the authors of other sorts of Pod > processors (i.e., authors of Pod utilities) Can it still accommodate the likes of Pod::Select and Pod::Usage? Few people know it, but one of the reasons I undertook writing the initial Pod::Parser was because I felt that writing usage messages in my Perl code was redundant when my POD's already had the necessary text and formatting. I wanted the equivalent of Pod::Text, but only for certain sections of the PODs. (that, and two other different but related applications led me to write Pod::Parser). I don't care so much if Pod::Select stays around (depends on who else needs it), but I definitely need Pod::Usage to still work, so that I can display short usage messages, and/or full-fledged manpages without any redundant usage text or redundant coding of stuff that the pod-parsing module already knows how to do. -- Brad Appleton <[EMAIL PROTECTED]> http://www.bradapp.net/ "Education is the ability to listen to almost anything without losing your temper or your self-confidence." -- Robert Frost
