Path: utzoo!utgpu!water!watmath!clyde!att!ucbvax!pasteur!ic.Berkeley.EDU!faustus
From: faustus@ic.Berkeley.EDU (Wayne A. Christopher)
Newsgroups: comp.lang.c
Subject: Re: #pragma does only half the job (was Re: Pragma and noalias)
Message-ID: <4580@pasteur.Berkeley.Edu>
Date: 21 Jul 88 11:01:03 GMT
References: <502@proxftl.UUCP> <381@proxftl.UUCP> <8176@brl-smoke.ARPA> <423@proxftl.UUCP> <23349@think.UUCP> <437@proxftl.UUCP> <1988Jul10.201104.27556@utzoo.uucp>
Sender: news@pasteur.Berkeley.Edu
Lines: 15

In article <502@proxftl.UUCP>, bill@proxftl.UUCP (T. William Wells) writes:
> "[a pragma] causes the implementation to behave in an
> implementation-defined manner...."
> 
> My reading of this says that a pragma changes the implementation,
> not (directly) the interpretation of the program.  However, the
> changed implementation must also be conforming.

You're right, this statement is sort of confusing, but when you think
about it, it has to mean that #pragma can cause a compiler to become
non-conforming.  Otherwise, #pragma noalias wouldn't be possible.
Telling the compiler that a set of parameters is noalias changes the
semantics of the function.

	Wayne