From owner-freebsd-arch Wed Jan 30 9:52:15 2002 Delivered-To: freebsd-arch@freebsd.org Received: from a96180.upc-a.chello.nl (a96180.upc-a.chello.nl [62.163.96.180]) by hub.freebsd.org (Postfix) with ESMTP id 111A737B417; Wed, 30 Jan 2002 09:52:08 -0800 (PST) Received: by a96180.upc-a.chello.nl (Postfix, from userid 1001) id 81887216E; Wed, 30 Jan 2002 18:52:02 +0100 (CET) Date: Wed, 30 Jan 2002 18:52:02 +0100 From: Jeroen Ruigrok/asmodai To: David O'Brien Cc: Terry Lambert , Poul-Henning Kamp , Jordan Hubbard , Dallas De Atley , arch@FreeBSD.ORG Subject: Re: __P macro question Message-ID: <20020130175201.GL22384@daemon.ninth-circle.org> References: <21280.1012384756@critter.freebsd.dk> <3C57C858.5FCC9453@mindspring.com> <20020130103326.GJ22384@daemon.ninth-circle.org> <20020130082247.A67274@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020130082247.A67274@dragon.nuxi.com> User-Agent: Mutt/1.3.24i Organisation: Ninth Circle Enterprises Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG -On [20020130 17:33], David O'Brien (obrien@FreeBSD.ORG) wrote: >On Wed, Jan 30, 2002 at 11:33:26AM +0100, Jeroen Ruigrok/asmodai wrote: >> Real hackers would use unifdef(1) for the #ifdef's. > >Someone please explain what is so bad with __P() ; or is this just the >small bike shed everyone can possibly undrestand sufficently to comment >on? I cannot fully oomment on the motiviations of others. For me it is the fact that there is no consistency. And the facts that: 1) two ANSI C standards have passed, lets put some effort in making use of the features they provide 2) it solves a problem not present in ANSI C, namely prototype support, see #1 3) it is a macro, macros tend to hide things [the preprocessor is a blunt tool to use] Also, commenting this to be a bikeshed while it is a serious request/question about code maintainability and clean-ups is not really constructive. Since you were friendly enough not to provide any constructive feedback whatsoever towards the issue other than labeling it a bikeshed, let me ask something in return: What is __P()'s higher motive and function that it needs to be present still? >> Anyway, are you scared of ANSI C? > >Are you scared of K&R C? Bad practices scare me. And K&R has been discussed to death on various fori before, and the large majority agreed that it should be replaced by ANSI C89 at least. If you do not start somewhere, you will never arrive anywhere. -- Jeroen Ruigrok van der Werven / asmodai / Kita no Mono / xMach coreteam asmodai@[wxs.nl|xmach.org], finger asmodai@ninth-circle.org http://www.softweyr.com/asmodai/ You're just like a vapor, that appears for a little while and vanishes one day... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message