TITLE: restrict keyword coming

(Newsgroups: comp.std.c++, 20 Aug 97)


UNKNOWN:

> Declaring A and B const does not tell the compiler that the
> values cannot change -- it tells it that it cannot change
> using that pointer, unless the pointer is cast to a pointer
> to nonconst. 


HENDERSON: Fergus Henderson <fjh@cs.mu.oz.au>

Yes, `const' doesn't promise that things won't be aliased.
The next revision of the C standard, C9X, will have a new keyword
"restrict" for that purpose, although it will probably be at least
a few years before many C or C++ compilers really support it.


[ The text above mentions aliasing. I believe that this
  code will be illegal

	T* someOtherPtr;
	restrict T* myPtr = ...;

	someOtherPtr = myPtr; // illegal
  -adc 
]