public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dirk.bonekaemper at dfs dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/56904] rejection of legal code in c++11 mode. (maybe namespace lookup problem) Date: Fri, 12 Apr 2013 07:23:00 -0000 [thread overview] Message-ID: <bug-56904-4-ycQaQsJjTb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56904-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56904 --- Comment #5 from dirk.bonekaemper at dfs dot de 2013-04-12 07:23:34 UTC --- First of all thanks for the fast reaction. Knowing the problem (obvious in hindsight :-) I already found another workaround: reopen the namespace. Thanks again.
prev parent reply other threads:[~2013-04-12 7:23 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-04-10 11:46 [Bug c++/56904] New: " dirk.bonekaemper at dfs dot de 2013-04-10 12:10 ` [Bug c++/56904] " jakub at gcc dot gnu.org 2013-04-11 2:53 ` jason at gcc dot gnu.org 2013-04-11 2:54 ` jason at gcc dot gnu.org 2013-04-11 9:16 ` jakub at gcc dot gnu.org 2013-04-12 7:23 ` dirk.bonekaemper at dfs dot de [this message]
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=bug-56904-4-ycQaQsJjTb@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).