OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   Re: [xml-dev] Why would MS want to make XML break on UNIX, Perl, Python

[ Lists Home | Date Index | Thread Index ]

On Thu, Dec 20, 2001 at 03:54:02PM +1100, Rick Jelliffe wrote:
> Sure, lets make XML unsuitable for use in UNIX pipes by allowing ^D.
> And for Perl and Python text-processing programs that use standard in and 
> expect EOF (^D or ^Z).

I cannot speak for all of the languages, but you certainly can send ^D
down a UNIX pipe. I think you are mixing up the tty processing of human
input and what is implemented in the OS/programming language. I don't
think many people will by typing in XML documents by hand down a pipe! :-)
Oh, and with UNIX I think you can send a ^D anyway by typing ^V^D
(depending on your shell).

I think if you said NUL your arguments may be stronger. I have less
confidence utilities like 'grep' would work correctly with a file
with NUL bytes in them. I agree that a strength of XML is that lots
of existing non-XML text utilities (grep, awk, per, etc) can be used
(carefully!!!) with XML. Allowing control characters directly in
the text stream would surely make one of them break.

Of course if you used � to encode NUL in text then that would not
be an issue. But I dislike this because its not in line with SGML.
I guese there is always the PI proposal - that is, use processing
instructions for control characters. This could be done as a SOAP
convention, for example. But it feels distinctly grungy.



News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS