开发者

C restrict with typedef

开发者 https://www.devze.com 2023-01-24 18:50 出处:网络
i\'m doing some code now and got some problem using restrict keyword. typedef int* pt; int foo(pt a, pt b)

i'm doing some code now and got some problem using restrict keyword.

typedef int* pt;

int foo(pt a, pt b)
{
 ... /* stuff */
}

What if I want to make a and b restricted? The code below failed:

typedef int* pt;

int foo(pt restrict a, pt restrict b)
{
 ... /*开发者_如何学Go stuff */
}

Thanks in advance.


Make sure you're compiling it using the C99 flag for your compiler. The restrict keyword doesn't exist in C89 C.


Having a quick look and reading this similar SO question, the code would be, as the keyword 'restrict' is not reserved keyword in C++ compilers, as indicated by the accepted answer in the above linky, either __restrict or __restricted__, again, check your compiler...

typedef int* __restrict pt;

int foo(pt a, pt b)
{
 ... /* stuff */
}


You need a "restricted pointer to integer" int * restrict p not a "pointer to restricted integer" restrict int *p so you will need to make another typedef. You can't "reach inside" the original one.

EDIT: While it's true that you can't reach inside the typedef and the modifier will always apply at the top level, in this case it turns out that you want the restrict at the top level. It's the inverse of what people usually run into with const: typedef char *char_ptr means const char_ptr (or char_ptr const, they're equivalent) both mean "constant pointer to char" not "pointer to constant char" which is what people want. (See also this SO thread: C++ typedef interpretation of const pointers )

So in this case I think typedef int *pt does mean that restrict pt means int * restrict pt. It's pretty easy to verify because gcc will complain about "invalid use of 'restrict'" for restrict int *x but not for restrict pt x.

0

精彩评论

暂无评论...
验证码 换一张
取 消