From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4015 invoked by alias); 3 Oct 2002 22:35:18 -0000 Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-help-owner@gcc.gnu.org Received: (qmail 4008 invoked from network); 3 Oct 2002 22:35:16 -0000 Received: from unknown (HELO gatekeeper.tait.co.nz) (202.37.96.11) by sources.redhat.com with SMTP; 3 Oct 2002 22:35:16 -0000 Received: from gatekeeper.tait.co.nz (localhost.localdomain [127.0.0.1]) by gatekeeper.tait.co.nz (8.11.2/8.9.3) with ESMTP id g93MZEF06391 for ; Fri, 4 Oct 2002 10:35:14 +1200 Received: from sunstorm.tait.co.nz (sunstorm.tait.co.nz [172.25.40.9]) by gatekeeper.tait.co.nz (8.11.2/8.9.3) with ESMTP id g93MZBY06379; Fri, 4 Oct 2002 10:35:11 +1200 Received: from parore (parore.tait.co.nz [172.25.140.12]) by sunstorm.tait.co.nz (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0H3F00DIPG2NWT@sunstorm.tait.co.nz>; Fri, 04 Oct 2002 10:35:11 +1200 (NZST) Date: Thu, 03 Oct 2002 15:35:00 -0000 From: John Carter Subject: Re: Visibility of C++ class private symbols (as compared to static) In-reply-to: <3D9AC923.8060207@web.de> X-Originating-IP: 127.0.0.1 X-X-Sender: johnc@parore To: Vivenzio Pagliari Cc: GCC Help Message-id: X-Complaints-to: /dev/null MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Content-transfer-encoding: 7BIT X-Priority: 4294967296 X-MSMail-priority: AbNormal X-Apparently-From: mars X-Contents: May contain traces of nuts. X-SW-Source: 2002-10/txt/msg00036.txt.bz2 On Wed, 2 Oct 2002, Vivenzio Pagliari wrote: > In theory, class Foo could be implemented in different compilation > units and thus require external linkage of the symbols. Even more, > the resulting object code could be split up in different libraries > (eg. Foo::bar(int) in libfoo1.so and Foo::s_ in libfoo2.so), > requiring eg. the entries in the dynamic symbol table. > But who does this or who needs this?? I suspect nobody does and nobody should, but to change the compiler so that it didn't would make it non-standard. (I can imagine one place where I would use that feature, suppose some of the class implementation is crafted by hand, some of it generated.) Conversely it shouldn't ever be a problem to you unless you are getting name space conflicts. At which point you should start using the namespace feature of the standard anyway. -- John Carter Phone : (64)(3) 358 6639 Tait Electronics Fax : (64)(3) 359 4632 PO Box 1645 Christchurch Email : john.carter@tait.co.nz New Zealand Good Ideas: Ruby - http://www.ruby-lang-org - The best of perl,python,scheme without the pain. Valgrind - http://developer.kde.org/~sewardj/ - memory debugger for x86-GNU/Linux Free your books - http://www.bookcrossing.com