From owner-freebsd-arch@FreeBSD.ORG Thu May 1 08:51:18 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 B56CE37B401; Thu, 1 May 2003 08:51:18 -0700 (PDT) Received: from mail.pcnet.com (mail.pcnet.com [204.213.232.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 06C5D43F75; Thu, 1 May 2003 08:51:18 -0700 (PDT) (envelope-from eischen@pcnet1.pcnet.com) Received: from pcnet1.pcnet.com (localhost [127.0.0.1]) by mail.pcnet.com (8.12.8/8.12.1) with ESMTP id h41FpGBg015153; Thu, 1 May 2003 11:51:16 -0400 (EDT) Received: from localhost (eischen@localhost)h41FpF1X015146; Thu, 1 May 2003 11:51:15 -0400 (EDT) Date: Thu, 1 May 2003 11:51:15 -0400 (EDT) From: Daniel Eischen To: "Andrey A. Chernov" In-Reply-To: <20030501154139.GA54878@nagual.pp.ru> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-arch@freebsd.org Subject: Re: `Hiding' libc symbols (was Re: cvs commit: src/lib/libc/gen ...) 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: Thu, 01 May 2003 15:51:19 -0000 On Thu, 1 May 2003, Andrey A. Chernov wrote: > On Thu, May 01, 2003 at 11:34:57 -0400, Daniel Eischen wrote: > > > > Wrong. We need _ tricks for threads libraries to work properly and > > was the reason it was added in the first place. BDE came up with > > the idea and it was reviewed by him. > > Threads is completely another issue. We can do ANY tricks threads needs > when it is NOT affects normal linking (under "normal" I mean preventing > standard namespace replacement from outside of libc). If current > replacement way for threads not allows preventing, it should be changed > somehow to be truely libc internal, i.e. not explotable from outside of > libc/libc_r/other threads libs. I'm not sure what you mean, but what we have works well. There may be times that we want to call the internal _foo() and other times were we want to call foo(). How are you going to build a tool that can tell the difference if you reference foo() in both places? IMHO, I don't think we should make libc developers dumb so that they don't have to know whether they should use foo() or _foo(). It's also easier to know which one is being referenced when you are reading the source. -- Dan Eischen