Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-lcc!ames!ucbcad!faustus
From: faustus@ucbcad.berkeley.edu (Wayne A. Christopher)
Newsgroups: comp.lang.c
Subject: Re: Reserved words in C
Message-ID: <1199@ucbcad.berkeley.edu>
Date: Mon, 5-Jan-87 17:01:00 EST
Article-I.D.: ucbcad.1199
Posted: Mon Jan  5 17:01:00 1987
Date-Received: Mon, 5-Jan-87 23:07:49 EST
References: <1524@hoptoad.uucp> <1016@zeus.UUCP> <5476@brl-smoke.ARPA>
Organization: CAD Group, U.C. Berkeley
Lines: 16

In article <5476@brl-smoke.ARPA>, gwyn@brl-smoke.ARPA (Doug Gwyn ) writes:
> Please note that a conforming implementation is not permitted
> to have any extensions that could alter the behavior of a
> strictly conforming program; one implication of this is that
> non-X3J11 entry points starting with anything other than _ must
> NOT be present in the implementation's standard C library.

If a standard library has a function called 'read' in it, I don't see how
this could alter the *behavior of the program*, although it may cause a 
program which would not otherwise compile to compile (i.e, the program
uses a function called 'read' that it doesn't define).  This is assuming
that the the library routines that want to use read call the function _read
instead.  I guess a "strictly conforming" flag would be useful in a
UNIX compiler though...

	Wayne