From owner-freebsd-arch@FreeBSD.ORG Tue May 6 08:25:57 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 5518C37B401 for ; Tue, 6 May 2003 08:25:57 -0700 (PDT) Received: from gw.nectar.cc (gw.nectar.cc [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 883B743FA3 for ; Tue, 6 May 2003 08:25:56 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.nectar.cc (Postfix) with ESMTP id 1A95DBB; Tue, 6 May 2003 10:25:56 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id 9FAAD78C69; Tue, 6 May 2003 10:25:57 -0500 (CDT) Date: Tue, 6 May 2003 10:25:57 -0500 From: "Jacques A. Vidrine" To: Terry Lambert Message-ID: <20030506152557.GD77708@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Terry Lambert , Peter Jeremy , freebsd-arch@freebsd.org References: <20030501182820.GA53641@madman.celabo.org> <20030505110601.H53365@beagle.fokus.fraunhofer.de> <20030505175426.GA19352@madman.celabo.org> <20030506092519.GA3158@cirb503493.alcatel.com.au> <3EB7CC73.9C61C27E@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3EB7CC73.9C61C27E@mindspring.com> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.3i-ja.1 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:25:57 -0000 On Tue, May 06, 2003 at 07:53:39AM -0700, Terry Lambert wrote: > Perhaps instead of asking how to prevent symbol replacement, one > should be asking how to get rid of incestuous functions in the > library implementation for standard library functions. > > No, I do not expect "_fmt" (or whatever) to go away from common > code in printf/sprintf/whatever. But I do expect it to be "_fmt" > instead of "fmt", i.e. in implementation space, rather than in > the symbol space legal for users to use. This is exactly what I wish to achieve. This is exactly the approach that I took with strlcpy [1]: the internal implementation is called `_strlcpy', while the exported symbol remains `strlcpy'. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se [1] Before I backed it out in an attempt to demonstrate good will.