Path: utzoo!utgpu!water!watmath!clyde!rutgers!ll-xn!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: unofficial X3J11 meeting notes
Keywords: ANSI C standard
Message-ID: <6850@brl-smoke.ARPA>
Date: 16 Dec 87 20:53:09 GMT
References: <9770@mimsy.UUCP> <6833@brl-smoke.ARPA> <4385@mnetor.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) )
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <4385@mnetor.UUCP> george@mnetor.UUCP (George Hart) writes:
>Will the standard also specify that attempts to create or use alternate
>handles for an object declared "noalias" are to generate compiler
>warnings/errors?

Only in certain contexts.  It's "too hard" (to use a technical
term) to determine whether this condition exists in general.
One thing I'm pretty sure IS allowed is to use an explicit
cast to copy a noalias pointer to a normal pointer.  This is
obviously risky stuff to be doing unless you have a firm grasp
of just what this aliasing business is all about; I would
suggest that the "typical programmer" (another technical term)
avoid using "noalias", just to play safe.