Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!bbn!papaya.bbn.com!rsalz
From: rsalz@bbn.com (Richard Salz)
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: pointer alignment when int != char *
Message-ID: <168@papaya.bbn.com>
Date: Tue, 8-Sep-87 17:19:30 EDT
Article-I.D.: papaya.168
Posted: Tue Sep  8 17:19:30 1987
Date-Received: Thu, 10-Sep-87 01:55:21 EDT
References: <493@its63b.ed.ac.uk> <6061@brl-smoke.ARPA> <3812@spool.WISC.EDU> <6397@brl-smoke.ARPA> <1122@gilsys.UUCP>
Reply-To: rsalz@papaya.bbn.com (Richard Salz)
Followup-To: comp.lang.c
Organization: BBN Laboratories, Cambridge MA
Lines: 23
Xref: mnetor comp.lang.c:4227 comp.unix.wizards:4147

In article <6397@brl-smoke.ARPA>, gwyn@brl-smoke.ARPA (Doug Gwyn ) explains
that ANSI doesn't specify open, read, write.

To which, in comp.unix.wizards (<1122@gilsys.UUCP>), mc68020@gilsys.UUCP
(Thomas J Keller) writes:
>   So in other words, Mr. Gwyn, what you are saying is that the ANSI C
>workgroup has taken it upon themselves to decide that "portable applications"
>programs have NO NEED to do other than straight sequential I/O on files,
>is this correct?  How very paternalistic of them! 

In general, Doug's postings have to be read the same way you read K&R or
the vintage Unix manuals (i.e., then the programmers wrote them, not a
separate techdoc department):  pay attention to every word, and give as
much note to what is not said, as to what is said.  It is not appropriate
for ANSI to specify the "Unix system-call" level, it is appropriate for
them to document the "standard I/O level."  Hence, X3J11 does specify
fseek.

Please read, and ponder, more carefully before you make snide, insulting
comments -- especially to or about people as useful to the net as Doug.
	/r$
-- 
For comp.sources.unix stuff, mail to sources@uunet.uu.net.