It was Friday, February 21, 2003 when Mark Overmeer took the soap box, saying: : Well, only the "see you a use for yourself" question of my e-mail is : answered. Apparently not for your code. What remains is that I see a : good use for myself (and many other OO modules). So the remaining : questions I ask to the members of this POD discussion group remain: : : 2) If I extend my concept into a usable module, would the "community" : accept it as alternative to plain POD?
No. You do want an alternative to POD, but you won't find many people lining up to use it. Someone mentioned JavaDoc, that is a possibility here. Or something XML based, which describes your class and it's recursive OO hierarchy. This is most certainly a special case. Having written several deep class based libraries (not on the CPAN, but documented with POD), I have not found the need to extend POD. The 'SEE ALSO' standard section does well for me. I also put a description of base classes, and sometimes sub classes, in the 'ABSTRACT' section. : 3) What name-space should my module take? Sounds like you really want something in your own distribution, under tools/, bin/, or utils/. Something like, 'build_pod.pl'. Casey West -- If you don't double-click me, I can't do anything. -- John Aniston, on how computers have taken over his life
