Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!ucbvax!agate!eos!ames!ncar!oddjob!mimsy!eneevax!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: standards development process
Message-ID: <7707@brl-smoke.ARPA>
Date: 16 Apr 88 04:43:25 GMT
References: <10314@tut.cis.ohio-state.edu> <1509@se-sd.sandiego.NCR.COM> <1510@se-sd.sandiego.NCR.COM> <543@vsi.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <543@vsi.UUCP> friedl@vsi.UUCP (Stephen J. Friedl) writes:
>While I may be free to not use |noalias| myself, I am required
>to interface with the library, most of whose routines have arguments
>declared with some permutation of |const| and/or |noalias|.  Because
>of this I think I think I have to have some nominal awareness of
>what these keywords do; the violent flamage against |noalias| leads
>me to believe that just pretending they are not there will get me
>into trouble.

As the January 1988 draft was worded, I believe you're correct.
The intent was that "normal" programmers could ignore the type
qualifiers in the library interface specs and continue to use
the functions as they're accustomed to.  This is something we'll
have to fix next week.