public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "boris at kolpackov dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/16468] [DR460] using-declaration of namespace name
Date: Mon, 12 Jul 2004 21:25:00 -0000	[thread overview]
Message-ID: <20040712212538.11227.qmail@sourceware.org> (raw)
In-Reply-To: <20040710210406.16468.boris@kolpackov.net>


------- Additional Comments From boris at kolpackov dot net  2004-07-12 21:25 -------
> Obviously, allowing a namespace name in a using-declaration inside a class 
> declaration does not make much sense.

This is a bogus argument! Only names from base are allowed in using-declaration
inside a class. Following your logic we should also ban somethin like

namespace n
{
  class foo {};
}; 

using n::foo;

Just because you cannot write

class bar
{
  using n::foo;
};


> 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?

Sure it can be achived by other means. I just don't see a reason why should it
be achived by other means? Here is the whole story: I have some amount of code
which works fine with gcc 3.x.y. Now I try to compile it with gcc 3.4.x and it
gives me an error about using-declaring namespace. Ok, I am thinking to myself,
it is probably either illegal or bug in gcc. So I am searching throug the
standard for any restrictions on the type of name that can be used in
using-declaration. The standard say none. Ok, I am thinking to myself, there
doesn't seem to be any good reason why one shouldn't using-declare a namespace
so it must be a bug in gcc. I am posting a bug report which is closed due to a
defect report (which, btw, hasn't been even voted upon) that says "we believe it
should be an error". Don't take it personaly, but if there is a defect report
that says everybody should start jumping off the roof, would you?

I posted a question to std.c++. I will follow up if anything comes out.

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16468


  parent reply	other threads:[~2004-07-12 21:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-10 21:04 [Bug c++/16468] New: " boris at kolpackov dot net
2004-07-11 14:51 ` [Bug c++/16468] " lerdsuwa at gcc dot gnu dot org
2004-07-12  6:39 ` [Bug c++/16468] [DR460] " pinskia at gcc dot gnu dot org
2004-07-12 15:54 ` boris at kolpackov dot net
2004-07-12 18:52 ` bangerth at dealii dot org
2004-07-12 21:25   ` Gabriel Dos Reis
2004-07-12 18:58 ` boris at kolpackov dot net
2004-07-12 20:53 ` bangerth at dealii dot org
2004-07-12 21:27   ` Gabriel Dos Reis
2004-07-12 21:25 ` gdr at acm dot org
2004-07-12 21:25 ` boris at kolpackov dot net [this message]
2004-07-12 21:32   ` Gabriel Dos Reis
2004-07-12 21:27 ` gdr at acm dot org
2004-07-12 21:32 ` gdr at acm dot org
2004-07-12 21:38 ` boris at kolpackov dot net
2004-07-13  4:19 ` bangerth at dealii dot org
2004-07-13  4:25 ` pinskia at gcc dot gnu dot org
2005-05-01  3:16 ` pinskia at gcc dot gnu dot org
2005-08-31 21:14 ` redi at gcc dot gnu dot org
     [not found] <bug-16468-5779@http.gcc.gnu.org/bugzilla/>
2005-12-07  4:34 ` pinskia at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040712212538.11227.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).