On 2 Oct 2000, at 10:35, Garrett Goebel wrote:
> From: John Porter [mailto:[EMAIL PROTECTED]]
> >
> > It would be very detrimental to perl's performance to have to do an
> > XML parse of every input source file.
>
> if the parser can skip between:
>
> =pod
>
> =cut
>
> it can certainly be m
From: John Porter [mailto:[EMAIL PROTECTED]]
>
> It would be very detrimental to perl's performance to have to do an
> XML parse of every input source file.
if the parser can skip between:
=pod
=cut
it can certainly be made to skip between:
On Sun, Oct 01, 2000 at 02:00:20PM -0500, J. David Blackstone wrote:
> While POD hasn't changed for several years, the QA group has a
> couple of ideas in the works to morph it in desireable ways that might
> be easier if POD were replaced with an XML DTD.
^
We must not forget that pod has one other requirement, which pure
embedded XML would violate: namely, perl (that's the perl interpreter)
must be able to detect and skip over pod sections very quickly.
It would be very detrimental to perl's performance to have to do an
XML parse of every input sour
I'd be all for the XML documentation idea, either as a replacement
for or as a substitute for POD. However, I'd like to note that if you
want XML documentation in your Perl code, POD really makes it easy:
=for XML (or DocBook, or whatever)
Simply require yourself to use only POD sections lik
