This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/16468] [DR460] using-declaration of namespace name
- From: "gdr at acm dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Jul 2004 21:27:27 -0000
- Subject: [Bug c++/16468] [DR460] using-declaration of namespace name
- References: <20040710210406.16468.boris@kolpackov.net>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From gdr at acm dot org 2004-07-12 21:27 -------
Subject: Re: [DR460] using-declaration of namespace name
bangerth at dealii dot org:
> As for your question of why a using-declaration should not be allowed to
> name namespace names: using declarations are used to inject declarations
> into a scope, for example into a class scope:
Right.
> class Base {
> void f(int);
> };
> class Derived : public Base {
> using Base::f;
> void f(double);
> };
> Obviously, allowing a namespace name in a using-declaration inside a class
> declaration does not make much sense.
Why doesn't it make sense? A definition is a declaration, so
if the namespace has an original-definition, it makes all sense
to bring its name into current scope.
I think I'm just confused what
> effect
> you try to achieve by allowing namespace names in using-declarations that
> can't be achieved by other means as well?
I'm confused as to why people would like to ban using-declaration
for namespace-names.
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16468