This is the mail archive of the
mailing list for the GCC project.
Re: RFC: C++: __attribute__((visibility)) for classes
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Matt Austern <austern at apple dot com>
- Cc: GCC <gcc at gcc dot gnu dot org>
- Date: 19 May 2004 21:13:42 +0200
- Subject: Re: RFC: C++: __attribute__((visibility)) for classes
- Organization: Integrable Solutions
- References: <A29AEF58-A9D1-11D8-B646-000393B2ABA2@apple.com>
Matt Austern <email@example.com> writes:
| I believe that any sensible solution has to be in the compiler.
| Asking users to explicitly list the symbols they want to hind is
| unreasonable: ordinary users shouldn't have to know which classes will
| need VTTs, construction vtables, and the like, and certainly shouldn't
| have to know the mangled names for those ghastly things. Even your
| average guru would probably get it wrong most of the time. I'm sure I
A question: Why would those symbols be "exported" in the first place?
If I understand correctly, they are emitted in the translation unit
that contains the key-method, wouldn't it make sense to have them
local to that translation unit?