__P macro

Saifi saifi at twincling.org
Thu Jun 8 07:27:42 UTC 2006


Hi:

Most of the racoon code uses __P macro.

and the __P macro is defined as -

#undef __P
#ifndef __P
#if __STDC__
#define __P(protos) protos
#else
#define __P(protos) ()
#endif
#endif

It seems to make many expressions difficult to read -
eg.

static int (*pkrecvf[]) __P((caddr_t *)) = {
 ...
}


What is the downside if this macro is not used in defining new function prototypes ?
(working with FreeBSD 5.4 and above with gcc 3.x compiler)

Thanks in advance.

thanks
Saifi

TWINCLING Society
http://www.twincling.org/


More information about the freebsd-questions mailing list