Date: Tue, 6 May 2003 01:20:27 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Dag-Erling Smorgrav <des@ofug.org> Cc: freebsd-arch@freebsd.org Subject: Re: `Hiding' libc symbols Message-ID: <20030505212027.GA41263@nagual.pp.ru> In-Reply-To: <xzpbryh3y0k.fsf@flood.ping.uio.no> 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> <xzpk7d53zu5.fsf@flood.ping.uio.no> <20030505205051.GA40572@nagual.pp.ru> <xzpbryh3y0k.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 05, 2003 at 23:05:15 +0200, Dag-Erling Smorgrav wrote: > "Andrey A. Chernov" <ache@nagual.pp.ru> writes: > > Better reject such error automatically at the linkage stage. Programmers > > are always free to redefine their functions in case of conflict. > > There must be something wrong with my MUA, as I can't see a patch > attached to your message. Could you please resend it? Which one do you mean? If one for affected ports, it is corresponding maintainers task. If one for libc, it is difficult (for me). The problem is that threads people do all that hiding in first place for their own needs. To simple unhide it, breaks threads. I think they must change replacement they need for functions to be truely internal, it makes all unhiding automatically.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030505212027.GA41263>