On Mon, 12 Nov 2001, Stephen Adkins wrote: > I have the following add-on questions. > > 1. Wesley - How do we configure the Makefile.PL so that the documentation > gets > separated from (stripped from?) the code at "make; make install" ? > (or did I misunderstand you?) > > 2. Matt - How do we configure Makefile.PL to invoke Pod::XML at > "make; make install"? > (http://search.cpan.org/doc/MSERGEANT/Pod-XML-0.93/XML.pm)
Why would you want to? Do you have a use-case for it? > 4. What would it take to enhance the core POD capabilities? Flying pigs. > I have the following recommendations. > > 1. Use inline POD where possible and separate POD files where reasonable > 2. We need to come up with a commenting/POD convention to allow for > specification > of at least all of the things that Javadoc allows you to specify > 3. Standard "make; make install" for a P5EE module should produce man > pages (perldoc), > html pages, PDF, and XML (for further flexible conversion/rendering) > 4. Our standard doc generation should produce output at least as nice as > Javadoc > (see an example at > http://java.sun.com/j2ee/sdk_1.3/techdocs/api/index.html) I hate to sound so negative, but good luck. You're going to need it. I've written highly detailed API docs using POD, and it's not pretty, it's not standard (i.e. no matter what you do, it won't produce correct results with "perldoc <Module>"), and it's a battle against the grain. Having said that, I hope you succeed. -- <Matt/> /|| ** Founder and CTO ** ** http://axkit.com/ ** //|| ** AxKit.com Ltd ** ** XML Application Serving ** // || ** http://axkit.org ** ** XSLT, XPathScript, XSP ** // \\| // ** mod_perl news and resources: http://take23.org ** \\// //\\ // \\
