Anonymous Namespaces

[Gabriel Dos Reis]

Alexandre Oliva <aoliva@redhat.com> writes:

| On Feb 11, 2004, Gabriel Dos Reis <gdr@integrable-solutions.net> wrote:
| 
| > Alexandre Oliva <aoliva@redhat.com> writes:
| 
| > | Here's my reasoning.  Please point out any flaws in it:
| > | 
| > | - If it's not a template, then the reference to the symbol is either
| > |   template-independent (so it's bound at parse time, and we can
| > |   determine immediately that the name can't be marked as local to the
| > |   translation unit), or it's referenced for being a template argument
| > |   passed to the exported template (in which case we know it can't be
| > |   used as an argument to the exported template in another translation
| > |   unit, because you can't reference the name in another unit, so you
| > |   can't get to that particular exported template instantiation, so the
| > |   name can remain local to the translation unit as well)
| 
| > I don't follow.  Argument dependent name lookup may hit a
| > non-template,
| 
| How?  I can only see it do so by means of typedefs, and this is the
| case we'd catch by the transitive closure case I mentioned.  Am I
| still missing anything?

Did you look at the example I gave?

-- Gaby