From owner-freebsd-arch Wed Jan 30 2:33:31 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 CDF5437B404 for ; Wed, 30 Jan 2002 02:33:27 -0800 (PST) Received: by a96180.upc-a.chello.nl (Postfix, from userid 1001) id 882DB216F; Wed, 30 Jan 2002 11:33:26 +0100 (CET) Date: Wed, 30 Jan 2002 11:33:26 +0100 From: Jeroen Ruigrok/asmodai To: Terry Lambert Cc: Poul-Henning Kamp , Jordan Hubbard , Dallas De Atley , arch@FreeBSD.ORG Subject: Re: __P macro question Message-ID: <20020130103326.GJ22384@daemon.ninth-circle.org> References: <21280.1012384756@critter.freebsd.dk> <3C57C858.5FCC9453@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3C57C858.5FCC9453@mindspring.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 11:22], Terry Lambert (tlambert2@mindspring.com) wrote: >Poul-Henning Kamp wrote: > >If the intent is no longer to act as a reference implementation >for various code, then perhaps we should reconsider and release >all of FreeBSD under the GPL, so it will be even more useless >as a use-agnostic reference implementation. > Acting as a reference implementation does _NOT_ mandate sticking to an old specification of C. Furthermore, putting it under GPL is a logical(?) step I cannot even imagine how you came to that. >More able hackers use scripts to remove "offensive" things >like "__P()" or even the contents of "#ifdef ALPHA" or other >noop code for the platform they are using, rather than >rendering the base code non-protable to all but their pet >machines. Real hackers would use unifdef(1) for the #ifdef's. Anyway, are you scared of ANSI C? Your argumentation is starting to border on the point of fright of moving forward to a standard a bit closer to what people are actually taught in schools nowadays. Most people don't even KNOW K&R C anymore, let alone use it. So moving to an ANSI standard in today's world might even be better to continue to act as a reference platform. >> Another useful method is keeping a "baseline patch" around which >> contains already looked over diffs and apply that in reverse before >> diff'ing. > >Won't work in the context of back-porting from an unstable >-current to a -stable a necessary patch, when you don't >want to have to drink the "kernel interrupt threads" and >other instability causing koolaid. Backporting is already a pain in the arse, having just recently been through backporting Scott Long's UDF driver to STABLE. And that's new code not even in CURRENT nor in STABLE, just making use of the APIs and supplied functionality. -- 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/ Hope sees the invisible, feels the intangible and achieves the impossible... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message