On Sat, 10 Nov 2001, Stephen Adkins wrote:
> Hi,
>
> What experiences to people have with using inline POD within
> the Module.pm as opposed to maintaining two files,
> Module.pm (for code) and Module.pod (for documentation)?
> What recommendations would you have for P5EE code?
>
> I would assume Inline POD is the way to go.
> I am wondering if anyone has experiences counter to this.
This is going to be an area of contention...
I think POD has to go for this project. At least in its default form.
We need something way more structured, that maintains API details to the
extreme, like JavaDOC does, only we want something easier/better than
JavaDOC.
I'd suggest XML for docs, in particular sdocbook (simple docbook), but I
know it gives people hives, so maybe an extended POD format would work
(but it starts to get real ugly when you extend it to this extent).
--
<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 **
\\//
//\\
// \\
