Question

In linux, container_of macro is enclosed in seemingly “extra” parentheses:

 #define container_of(ptr, type, member) ({ \
                const typeof( ((type *)0)->member ) *__mptr = (ptr); 
                (type *)( (char *)__mptr - offsetof(type,member) );})

Instead of it, can we just use

 #define container_of(ptr, type, member) { \
                const typeof( ((type *)0)->member ) *__mptr = (ptr); 
                (type *)( (char *)__mptr - offsetof(type,member) );}

?

Are the parentheses mandatory or are they just for precaution?

Answer 1

It’s necessary. One of the “tricks” used is GCC’s statement expressions that require this ‘strange’ ({ code }) syntax.

Code that uses this macro wouldn’t compile without that in most use cases (and it’s not valid C).

See also:
Rationale behind the container_of macro in linux/list.h

And: container_of by Greg Kroah-Hartman.