From owner-cvs-all Mon Sep 11 5:35: 4 2000 Delivered-To: cvs-all@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 9308437B422; Mon, 11 Sep 2000 05:34:51 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id XAA07173; Mon, 11 Sep 2000 23:33:59 +1100 Date: Mon, 11 Sep 2000 23:33:57 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Boris Popov Cc: Doug Rabson , John Baldwin , Doug Rabson , cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/sys ktr.h In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 11 Sep 2000, Boris Popov wrote: > On Mon, 11 Sep 2000, Bruce Evans wrote: > > > > I'll replace it with KASSERT-like definition: > > > > > > #define NULLFSDEBUG(args) printf args > > > > > > with appropriate changes to the rest of the code. > > > > I had almost accepted it. Is the only problem with the KASSERT-like > > definition that double parentheses must be used when it is invoked? > > This has the same problem as ITR* -- it messes up all invocations > > of the macros. > > I think double parentheses more readable in compare with three > lines of #ifdef/blah/#endif. In this case they are at the beginning and > the end of invocation, so code doesn't turn to a mess. I meant that requiring double parentheses or arg counts in the macro names is messy compared with not requiring these. Then when variadic macros become portable, there will be too many invocations to change. Actually, the arg counts are a bit worse -- they have to be counted manually. Parentheses are only hard to count when there are more than 2 of them :). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message