From owner-freebsd-arch@FreeBSD.ORG Tue Mar 13 18:52:20 2007 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 75AEA16A403 for ; Tue, 13 Mar 2007 18:52:20 +0000 (UTC) (envelope-from julian@elischer.org) Received: from outT.internet-mail-service.net (outT.internet-mail-service.net [216.240.47.243]) by mx1.freebsd.org (Postfix) with ESMTP id 4D5DC13C46A for ; Tue, 13 Mar 2007 18:52:20 +0000 (UTC) (envelope-from julian@elischer.org) Received: from mx0.idiom.com (HELO idiom.com) (216.240.32.160) by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP; Tue, 13 Mar 2007 11:25:20 -0700 Received: from [192.168.2.5] (home.elischer.org [216.240.48.38]) by idiom.com (Postfix) with ESMTP id 7683C1260C2; Tue, 13 Mar 2007 11:43:05 -0700 (PDT) Message-ID: <45F6F0B9.8080702@elischer.org> Date: Tue, 13 Mar 2007 11:43:05 -0700 From: Julian Elischer User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221) MIME-Version: 1.0 To: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= References: <39968.1173776514@critter.freebsd.dk> <864pop8pnt.fsf@dwp.des.no> In-Reply-To: <864pop8pnt.fsf@dwp.des.no> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: arch@freebsd.org, Poul-Henning Kamp Subject: Re: bikeshed proposal X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Mar 2007 18:52:20 -0000 Dag-Erling Smørgrav wrote: > Poul-Henning Kamp writes: >> It has always bothered me that some of the TAILQ macros need to >> know the struct name of the header type. >> [...] >> Obviously this is bikeshed fodder, but given how big a help >> is programming-wise, and given that those four macros are comparatively >> seldomly used, I will propose to remove this wart from >> under the banner of computer science in general and suffer the minor >> backwards compatibility issues it will cause. > > The backwards compatibility issues may be minor, but the > compatibility-with-other-BSDs issues aren't... > > DES please discuss this with Kirk as my memory is that he had a hand in the original implementation (or at least knew the story).