From owner-freebsd-questions@FreeBSD.ORG Thu Jun 8 07:27:29 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EDE4916CD0D for ; Thu, 8 Jun 2006 05:15:49 +0000 (UTC) (envelope-from saifi@twincling.org) Received: from coolhost77.com (coolhost77.com [203.194.209.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29F2343D46 for ; Thu, 8 Jun 2006 05:15:48 +0000 (GMT) (envelope-from saifi@twincling.org) Received: (qmail 20199 invoked by uid 514); 8 Jun 2006 05:15:46 -0000 Message-ID: <20060608051546.27320.qmail@coolhost77.com> From: "=?iso-8859-1?Q?Saifi?=" To: freebsd-questions@freebsd.org Date: Thu, 08 Jun 2006 10:45:46 +0530 MIME-Version: 1.0 X-Mailer: WebMail 2.5 X-Originating-IP: 59.93.56.140 X-Originating-Email: saifi@twincling.org Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Subject: __P macro X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: =?iso-8859-1?Q?Saifi?= List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jun 2006 07:27:42 -0000 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/