Date: Thu, 08 Jun 2006 10:45:46 +0530 From: "=?iso-8859-1?Q?Saifi?=" <saifi@twincling.org> To: freebsd-questions@freebsd.org Subject: __P macro Message-ID: <20060608051546.27320.qmail@coolhost77.com>
next in thread | raw e-mail | index | archive | help
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/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060608051546.27320.qmail>