From owner-freebsd-arch@FreeBSD.ORG Thu May 8 09:30:19 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8524637B404; Thu, 8 May 2003 09:30:06 -0700 (PDT) Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7F6343F93; Thu, 8 May 2003 09:30:05 -0700 (PDT) (envelope-from archie@dellroad.org) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id JAA58753; Thu, 8 May 2003 09:17:38 -0700 (PDT) Received: from arch20m.dellroad.org (localhost [127.0.0.1]) by arch20m.dellroad.org (8.12.8/8.12.8) with ESMTP id h48GHcNU008634; Thu, 8 May 2003 09:17:38 -0700 (PDT) (envelope-from archie@arch20m.dellroad.org) Received: (from archie@localhost) by arch20m.dellroad.org (8.12.8/8.12.8/Submit) id h48GHcZT008633; Thu, 8 May 2003 09:17:38 -0700 (PDT) From: Archie Cobbs Message-Id: <200305081617.h48GHcZT008633@arch20m.dellroad.org> In-Reply-To: <20030508161223.GL1869@survey.codeburst.net> To: Paul Richards Date: Thu, 8 May 2003 09:17:38 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII cc: "Jacques A. Vidrine" cc: David O'Brien cc: freebsd-arch@FreeBSD.ORG Subject: Re: Re: `Hiding' libc symbols X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 May 2003 16:30:20 -0000 Paul Richards wrote: > > But gee, the problem is that the ports themselves are not really > > in error, unless one is a standards fascist that believes that an > > application can never define any function that might be in some > > standard's namespace. > > Any C code that isn't written according to the standard that defines > C is broken. > > There's just no argument to be made that FreeBSD should be hacked > to support C code that is written by programmers who haven't bothered > to learn the rules of C properly. Agreed... and even if you *do* believe FreeBSD should accomodate such broken applications, the place to put the hack is in the port, not in the base system. -Archie __________________________________________________________________________ Archie Cobbs * Precision I/O * http://www.precisionio.com