Restricted arrays

[Spiros Bousbouras]

Is there a way to mimick restricted pointers
using array syntax ? So I'm looking for something
to add to a statement such as "int arr[50]" which
will tell the compiler that I will only access the contents of the
array through arr. If I was using
pointers I would do for example
int * restrict p = malloc(50 * sizeof(int))

Is there a way to do the same thing using
arrays ?

 

[Keith Thompson]

Is there a way to mimick restricted pointers
using array syntax ? So I'm looking for something
to add to a statement such as "int arr[50]" which
will tell the compiler that I will only access the contents of the
array through arr. If I was using
pointers I would do for example
int * restrict p = malloc(50 * sizeof(int))

Is there a way to do the same thing using
arrays ?

I don't think so.

A possible workaround might be:

int do_not_refer_to_this[50];
int * restrict p = do_not_refer_to_this;

Of course p is not an array, so sizeof p won't give you the size of
the array as it would if you could do this directly.

 

[bigcaterpillar]

if use "int array[50] in local fuction" .when the program
run ,compiler allocates memory space in stack area.
if you use malloc function ,compiler acclocates memory space in heap
area.
"int array[50]" array is a constant pointer ,you can't change it.
"malloc..." you can change its direction and point somewhere.

 

[Szabolcs Borsanyi]

Is there a way to mimick restricted pointers
using array syntax ? So I'm looking for something
to add to a statement such as "int arr[50]" which
will tell the compiler that I will only access the contents of the
array through arr...

I am not quite sure if this works out, the experts will surely know...
If you declare your array as
struct { int a; } arr[50];
then the aliasing rules will restrict the access to it either through
the struct above (e.g. arr[3].a) or through a pointer to char.

Szabolcs