From owner-freebsd-arch Wed Jan 30 2:31:54 2002 Delivered-To: freebsd-arch@freebsd.org Received: from mass.dis.org (dhcp45-21.dis.org [216.240.45.21]) by hub.freebsd.org (Postfix) with ESMTP id 223D337B402 for ; Wed, 30 Jan 2002 02:31:51 -0800 (PST) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.6) with ESMTP id g0UAW1b01550 for ; Wed, 30 Jan 2002 02:32:02 -0800 (PST) (envelope-from msmith@mass.dis.org) Message-Id: <200201301032.g0UAW1b01550@mass.dis.org> X-Mailer: exmh version 2.5 07/13/2001 with nmh-1.0.4 To: arch@FreeBSD.ORG Subject: Re: __P macro question In-reply-to: Your message of "Wed, 30 Jan 2002 02:20:18 PST." <3C57C8E2.5D7F9DCC@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Jan 2002 02:32:01 -0800 From: Michael Smith 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 > For what it's worth, I consider __P() to be incredibly ugly, > but to be a necessary evil to ensure code portability. It's inadequate, and such a trivial aid to "portability" compared to its nuisance value otherwise that maintaining it makes no sense. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message