• 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: Fri, 21 Dec 2001 06:07:07 -0500 (EST)
• Cc: xml-dev@l...
• In-reply-to: <027101c189bc$a72f0ca0$4bc8a8c0@A...> from Rick Jelliffeat "Dec 21, 2001 12:13:09 pm"

Rick Jelliffe scripsit:

>  From: "John Cowan" <cowan@m...>
>  
> > > 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 :-) ).
>  
> Where did I say it was a distinction built into UNIX?  
> 
> I said "it is because the specific programs".  And I gave examples of the 
> APIs from C++, Python, Haskell and Perl where this can happen.

In their Unix implementations?  No.  No Unix stdio treats any incoming byte
as EOF.

-- 
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

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

• Prev by Date: Re: Time to put SGML out to pasture? (was RE: Why would MS want to make XML break on UNIX, Perl, Python, etc ?)
• Next by Date: Re: Supporting Unicode
• 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