From: Myers, Dirk [mailto:[EMAIL PROTECTED]] > > Maybe I'm reading too much into the comment, but I thought > the big deal was that the example given was not only > verbose, but wouldn't parse correctly: > > (from the section you elided:) > > > > > <Author>Eliott P. Squibb</Author> > > > > <Maintainer>Joe Blogg</Author> > > Whoops. We need a </Maintainer> tag there. Yes, and it'd be patently obvious to the parser where the problem is and easier to generate a specific and meaningful warnings to boot. Not to mention if you use a gui editor incorporated color coding, it'd be easier to read and see errors. Emacs cPerl doesn't handle pod very well... anyone know why that is? > True. And the fact that the example wasn't written properly isn't a > conclusive proof that it's not easy to do. But it isn't exactly an > encouraging sign, either. Can you see the problematic extra space here? No... I didn't think so... =pod =head1 Header =cut
- Re: RFC 357 (v1) Perl should use XML for d... Robin Berjon
- Re: RFC 357 (v1) Perl should use XML ... John Porter
- Re: RFC 357 (v1) Perl should use XML for d... John Siracusa
- Re: RFC 357 (v1) Perl should use XML ... John Porter
- Re: RFC 357 (v1) Perl should use ... John Siracusa
- Re: RFC 357 (v1) Perl should use ... John Porter
- Re: RFC 357 (v1) Perl should use ... Peter Scott
- Re: RFC 357 (v1) Perl should use XML for documentation... Adam Turoff
- Re: RFC 357 (v1) Perl should use XML for documenta... Philip Newton
- RE: RFC 357 (v1) Perl should use XML for documentation inst... Myers, Dirk
- RE: RFC 357 (v1) Perl should use XML for documentation inst... Garrett Goebel
- RE: RFC 357 (v1) Perl should use XML for documentation inst... Garrett Goebel
- RE: RFC 357 (v1) Perl should use XML for documentation inst... David Grove
- Re: RFC 357 (v1) Perl should use XML for documentation... Johan Vromans
- Re: RFC 357 (v1) Perl should use XML for documenta... Bart Lateur
- Re: RFC 357 (v1) Perl should use XML for docum... Johan Vromans