On Mon, Oct 02, 2000 at 02:44:56PM -0600, John Barnette wrote: > But why extend the syntax for such a niche application? > > * POD can be easily converted to XML. > * POD can contain XML. > * Advanced concepts that POD cannot contain that the XML junkies > might want to be used can be embedded. (=for XML) Now, if I could use POD to get the job done more lazily, but switch to XML if I needed something more than pod can do (tables more sophisticated than can be tersely expressed in monospace ASCII being the only one so far) then I'd be happy. Oh, and my code would be more likely to be documented full stop than if I had to fight XML. I speak only for myself here. (oh, and my boss, who thought the same) Nicholas Clark
- RE: RFC 357 (v1) Perl should use XML for documentation inst... David Grove
- RE: RFC 357 (v1) Perl should use XML for documentation... Garrett Goebel
- Re: RFC 357 (v1) Perl should use XML for documentation... Johan Vromans
- RE: RFC 357 (v1) Perl should use XML for documentation... Garrett Goebel
- RE: RFC 357 (v1) Perl should use XML for documenta... John Barnette
- Re: RFC 357 (v1) Perl should use XML for docum... Nicholas Clark
- Re: RFC 357 (v1) Perl should use XML for d... John Porter
- Re: RFC 357 (v1) Perl should use XML for docum... John Siracusa
- Re: RFC 357 (v1) Perl should use XML for d... John Porter
- Re: RFC 357 (v1) Perl should use XML ... Robin Berjon
- Re: RFC 357 (v1) Perl should use XML ... John Siracusa
- Re: RFC 357 (v1) Perl should use XML ... Peter Scott
- Re: RFC 357 (v1) Perl should use XML for documenta... Adam Turoff
- Re: RFC 357 (v1) Perl should use XML for docum... Philip Newton
- RE: RFC 357 (v1) Perl should use XML for documentation... Myers, Dirk
- RE: RFC 357 (v1) Perl should use XML for documentation... Garrett Goebel