On Jul 14, 2006, at 3:01 PM, Gabriel Dos Reis wrote:
That would mirror how C++ handles classes in unnamed namspaces. In other words, the visibility would have to be part of the mangled name.
Can't do that and preserve the abi, also, there is no concept in gcc currently to so name it, and what's worse, in general, it is just impossible given how people use gcc. You'd require that the decision of which shared library a compilation unit is to go into be fixed before compilation, currently, that isn't so required.
All in all, we should just agree to not worry about non-merged typeinfo name, or remove support for it.
