• To: Rick Jelliffe <ricko@a...>
• Subject: Re: Why would MS want to make XML break on UNIX, Perl, Python,etc ?
• From: John Cowan <cowan@m...>
• Date: Thu, 20 Dec 2001 05:43:04 -0500 (EST)
• Cc: xml-dev@l...
• In-reply-to: <015e01c18920$a668f660$4bc8a8c0@A...> from Rick Jelliffeat "Dec 20, 2001 05:36:26 pm"

Rick Jelliffe scripsit:

> So if you can send ^D down your UNIX pipes, it is because the specific programs in the 
> pipeline happen to be reading the input stream in binary mode not text mode.  

There is no such distinction at all in Unix.  If some stdio operations on
Windows terminate when they see a #x19 in the input, it is purely for CP/M
compatibility (no :-) ).

-- 
John Cowan           http://www.ccil.org/~cowan              cowan@c...
Please leave your values        |       Check your assumptions.  In fact,
   at the front desk.           |          check your assumptions at the door.
     --sign in Paris hotel      |            --Miles Vorkosigan

• Follow-Ups:
  • Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
    • From: "Rick Jelliffe" <ricko@a...>

• References:
  • Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
    • From: "Rick Jelliffe" <ricko@a...>

• Prev by Date: RE: embedded html
• Next by Date: RE: embedded html
• Previous by thread: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• Next by thread: Re: Why would MS want to make XML break on UNIX, Perl, Python, etc ?
• Index(es):
  • Date
  • Thread