• To: xml-dev@l...
• Subject: Re: NULL in C (was RE: Why would MS want to make XML break on UNIX, Perl, Python, etc ?)
• From: Richard Tobin <richard@c...>
• Date: Sat, 22 Dec 2001 00:07:56 GMT
• Cc:
• In-reply-to: <5C39F806F9939046B4B1AFE652500A3A478B77@R...>
• Organization: HCRC, University of Edinburgh

>This is going off-topic a bit, but two ways to represent 0C in C strings
>are:

Yes, there are certainly reasonable ways to do it.  If nul had been
included in XML 1.0 we would have bitten the bullet and used one of
them.  But changing it now would mean substantial changes to every
application whose parser currently uses a nul-terminated string
representation.

-- Richard

• Follow-Ups:
  • Re: NULL in C (was RE: Why would MS want to makeXML break on UNIX, Perl, Python, etc ?)
    • From: David Brownell <david-b@p...>

• References:
  • NULL in C (was RE: Why would MS want to make XML break on UNIX, Perl, Python, etc ?)
    • From: "Michael Rys" <mrys@m...>

• Prev by Date: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• Next by Date: XML - XML Transformations
• Previous by thread: NULL in C (was RE: Why would MS want to make XML break on UNIX, Perl, Python, etc ?)
• Next by thread: Re: NULL in C (was RE: Why would MS want to makeXML break on UNIX, Perl, Python, etc ?)
• Index(es):
  • Date
  • Thread