Path: utzoo!mnetor!uunet!husc6!mailrus!tut.cis.ohio-state.edu!bloom-beacon!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Newsgroups: comp.lang.c
Subject: Re: Binary I/O on stdin/stdout?
Message-ID: <2605@bsu-cs.UUCP>
Date: 12 Apr 88 14:42:35 GMT
References: <302@goofy.megatest.UUCP> <225800017@uxe.cso.uiuc.edu> <8042@elsie.UUCP> <865@cresswell.quintus.UUCP>
Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 12
Summary: caveat emptor

In article <865@cresswell.quintus.UUCP> ok@quintus.UUCP (Richard A. O'Keefe)
writes:
>...the point of the discussion was precisely that the
>ability to do binary I/O on stdin/stdout was something that some people
>needed and didn't appear to be available in dpANS.

ANSI can't change this for you.  ANSI is obliged to humor existing broken
software environments.

But you aren't!  Let your buying dollar make a statement.
-- 
Rahul Dhesi         UUCP:  <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!dhesi