Implementing "restrict", and other alias questions

[Richard Henderson]

On Sun, Dec 28, 1997 at 09:17:37PM +0100, Martin von Loewis wrote:
> struct foo{
>   struct foo * restrict next;
>   int value;
> };
> 
> Again, the implementation is free to ignore the declaration - it
> should not reject it.

I agree that this is the proper attitude to take.

> Another issue is references: Is
> 
>   void f(class C restrict &);
> 
> valid. If so, how does restrict interfere with function overloading?

In the same way that `register' interferes, that is, not at all.


r~