From owner-freebsd-arch@FreeBSD.ORG Mon May 5 16:18:48 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 9D3BA37B401; Mon, 5 May 2003 16:18:48 -0700 (PDT) Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4D57F43F75; Mon, 5 May 2003 16:18:47 -0700 (PDT) (envelope-from ache@pobrecita.freebsd.ru) Received: from pobrecita.freebsd.ru (ache@localhost [127.0.0.1]) by nagual.pp.ru (8.12.9/8.12.9) with ESMTP id h45NIjrO044650; Tue, 6 May 2003 03:18:46 +0400 (MSD) (envelope-from ache@pobrecita.freebsd.ru) Received: (from ache@localhost) by pobrecita.freebsd.ru (8.12.9/8.12.9/Submit) id h45NIjZ5044647; Tue, 6 May 2003 03:18:45 +0400 (MSD) Date: Tue, 6 May 2003 03:18:42 +0400 From: "Andrey A. Chernov" To: "Jacques A. Vidrine" , Dag-Erling Smorgrav , freebsd-arch@FreeBSD.org Message-ID: <20030505231837.GA44533@nagual.pp.ru> References: <20030501182820.GA53641@madman.celabo.org> <20030501191027.GA53801@madman.celabo.org> <20030505110601.H53365@beagle.fokus.fraunhofer.de> <20030505175426.GA19352@madman.celabo.org> <20030505205051.GA40572@nagual.pp.ru> <20030505231135.GA21953@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030505231135.GA21953@madman.celabo.org> User-Agent: Mutt/1.5.4i Subject: 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: Mon, 05 May 2003 23:18:48 -0000 On Mon, May 05, 2003 at 18:11:35 -0500, Jacques A. Vidrine wrote: > applications that (IMHO most legitimately, some not) define symbols > that are technically in some standard's space, such as `snprintf', > `strlcpy', `accept', `close', ... ? ``Fix'' them all? Throw them > away? Fix them all. It is as easy as putting #define printf myprintf somewhere into headers or even into CC flags. When this task is spreaded among corresponding ports maintainers, the number for each of them will be not too big. > What about applications that are already compiled? Leave them as is. I mean linker time error, not runtime. > I think such fascism would result in us behaving in a very un-UNIX > fashion. And I think just opposite.