Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 29 Apr 2003 20:57:48 -0500
From:      "Jacques A. Vidrine" <nectar@FreeBSD.org>
To:        src-committers@FreeBSD.org, cvs-src@FreeBSD.org, cvs-all@FreeBSD.org
Cc:        Dag-Erling Smorgrav <des@ofug.org>
Subject:   Re: cvs commit: src/lib/libc/gen check_utility_compat.c confstr.c fmtmsg.c getgrent.c getpwent.c src/lib/libc/include namespace.h un-namespace.h src/lib/libc/locale setlocale.c src/lib/libc/net getaddrinfo.c gethostbydns.c getnameinfo.c hesiod.c ...
Message-ID:  <20030430015748.GA19911@madman.celabo.org>
In-Reply-To: <20030430002014.GA1190@dragon.nuxi.com>
References:  <200304292113.h3TLDoGF072965@repoman.freebsd.org> <xzp65oxrn3e.fsf@flood.ping.uio.no> <20030430002014.GA1190@dragon.nuxi.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Apr 29, 2003 at 05:20:14PM -0700, David O'Brien wrote:
> On Tue, Apr 29, 2003 at 11:49:09PM +0200, Dag-Erling Smorgrav wrote:
> > Jacques Vidrine <nectar@FreeBSD.org> writes:
> > >   Log:
> > >   `Hide' strlcpy and strlcat (using the namespace.h / __weak_reference
> > >   technique) so that we don't wind up calling into an application's
> > >   version if the application defines them.
> > 
> > We should probably do this for every libc function that is used within
> > libc...
> 
> No we shouldn't.  If I understand you correctly, it prevents me from
> linking in my own malloc()/free() and having the entire system use it.

It just means that you'd have to name your implementations e.g.
_malloc and _free, also.    But still, I suppose you have a point ...
there /may/ be some functions that /should not/ be `hidden'.

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?20030430015748.GA19911>