From owner-freebsd-arch@FreeBSD.ORG Tue May 6 08:42:13 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 CA91837B401 for ; Tue, 6 May 2003 08:42:13 -0700 (PDT) Received: from Daffy.timing.com (ns2.timing.com [206.168.13.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id C951B43FA3 for ; Tue, 6 May 2003 08:42:12 -0700 (PDT) (envelope-from ben@timing.com) Received: from piglet.timing.com (oink@piglet.timing.com [206.168.13.178]) by Daffy.timing.com (8.11.3/8.11.3) with ESMTP id h46Fg6H27461; Tue, 6 May 2003 09:42:06 -0600 (MDT) (envelope-from ben@timing.com) Received: from piglet.timing.com (oink@localhost.timing.com [127.0.0.1]) by piglet.timing.com (8.12.6/8.12.6) with ESMTP id h46Fg6g2016266; Tue, 6 May 2003 09:42:06 -0600 (MDT) (envelope-from ben@piglet.timing.com) Received: (from ben@localhost) by piglet.timing.com (8.12.6/8.12.6/Submit) id h46Fg4Fk016263; Tue, 6 May 2003 09:42:04 -0600 (MDT) From: Ben Mesander MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16055.55244.458061.779430@piglet.timing.com> Date: Tue, 6 May 2003 09:42:04 -0600 To: Daniel Eischen In-Reply-To: References: <20030505225021.GA43345@nagual.pp.ru> X-Mailer: VM 7.00 under Emacs 21.2.95.2 cc: "Andrey A. Chernov" cc: Dag-Erling Smorgrav cc: freebsd-arch@freebsd.org 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: Tue, 06 May 2003 15:42:14 -0000 Daniel Eischen writes: > On Tue, 6 May 2003, Andrey A. Chernov wrote: > > On Mon, May 05, 2003 at 18:14:45 -0400, Daniel Eischen wrote: > > Especially when I don't understands threads details. At this stage we just > > discuss here how to make things better. My point will be clear answering > > on this simple question: > > > > What produce less errors in application and libraries? > > a) Allow application to replace any standard function. > > I thought Jacques found lots of ports that replaced standard > functions... In addition to ports which override libc functions like printf() for ease of porting, there are important ports, such as the Boehm garbage collector for C/C++ or electric fence, which _depend_ upon the ability to override libc functions such as malloc() and free(). Whatever decision is eventually made must allow such ports to function. This has been brought up once before, but I do not see how any of the advocates for change have addressed it. --Ben