Date: Tue, 6 May 2003 10:29:26 -0500 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: Harti Brandt <brandt@fokus.fraunhofer.de> Cc: freebsd-arch@FreeBSD.org Subject: Re: Re: `Hiding' libc symbols Message-ID: <20030506152926.GG77708@madman.celabo.org> In-Reply-To: <20030506093754.B838@beagle.fokus.fraunhofer.de> References: <20030501182820.GA53641@madman.celabo.org> <XFMail.20030501144502.jhb@FreeBSD.org> <20030501191027.GA53801@madman.celabo.org> <20030505110601.H53365@beagle.fokus.fraunhofer.de> <20030505175426.GA19352@madman.celabo.org> <20030506093754.B838@beagle.fokus.fraunhofer.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 06, 2003 at 09:46:12AM +0200, Harti Brandt wrote: > No. If I define my own printf() I want that printf to be called even by > library internal calls. No, you really don't. If you do, then you use the techniques that dozens of applications already use today. `Hiding' libc symbols do not get in the way of these techniques. printf is an incredibly bad example, of course. What makes you think there are any calls to printf in libc anyway? Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030506152926.GG77708>