public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/23594] namespace typedef and global typedef name the same type, using kills global
Date: Sat, 27 Aug 2005 18:37:00 -0000	[thread overview]
Message-ID: <20050827170505.26119.qmail@sourceware.org> (raw)
In-Reply-To: <20050827125841.23594.yuri@tsoft.com>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-08-27 17:05 -------
(In reply to comment #2)
> (In reply to comment #1)
> ...
> > PS. the semicolon after the end of the namespace really makes this code
> invalid but since this is not 
> ...
> I didn't get why semicolon makes it invalid.
> I thought semicolon is allowed between any statements.
Because namespace (and extern "C") blocks are not statements.

-- 


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


  parent reply	other threads:[~2005-08-27 17:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-27 13:53 [Bug c++/23594] New: namespace typedef kills non-namespace typedef when "using" it yuri at tsoft dot com
2005-08-27 15:23 ` [Bug c++/23594] namespace typedef and global typedef name the same type, using kills global pinskia at gcc dot gnu dot org
2005-08-27 17:05 ` yuri at tsoft dot com
2005-08-27 18:37 ` pinskia at gcc dot gnu dot org [this message]
     [not found] <bug-23594-6649@http.gcc.gnu.org/bugzilla/>
2005-11-09 17:03 ` pinskia at gcc dot gnu dot org
2005-11-09 17:25 ` pinskia at gcc dot gnu dot org
2010-06-02 17:37 ` paolo dot carlini at oracle dot com
2010-06-02 18:24 ` jason at gcc dot gnu dot org
2010-06-02 19:25 ` jason 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=20050827170505.26119.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).