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++/19377] Using declaration in "private" part causes "protected" diagnostic Date: Tue, 11 Jan 2005 17:08:00 -0000 [thread overview] Message-ID: <20050111170805.17077.qmail@sourceware.org> (raw) In-Reply-To: <20050111161422.19377.redi@gcc.gnu.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-11 17:08 ------- No this is valid code. We don't implement full using semantics. This might be related to PR 6936. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 Keywords| |rejects-valid Last reconfirmed|0000-00-00 00:00:00 |2005-01-11 17:08:01 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19377
next prev parent reply other threads:[~2005-01-11 17:08 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-11 16:25 [Bug c++/19377] New: " redi at gcc dot gnu dot org 2005-01-11 17:08 ` pinskia at gcc dot gnu dot org [this message] 2005-01-12 10:46 ` [Bug c++/19377] " lerdsuwa at gcc dot gnu dot org 2005-05-01 3:34 ` pinskia at gcc dot gnu dot org [not found] <bug-19377-4@http.gcc.gnu.org/bugzilla/> 2010-11-12 15:08 ` fabien at gcc dot gnu.org 2011-11-27 21:44 ` fabien at gcc dot gnu.org 2012-04-15 17:11 ` manu at gcc dot gnu.org 2012-04-15 17:18 ` pinskia at gcc dot gnu.org 2012-04-15 17:42 ` manu at gcc dot gnu.org 2012-04-15 18:24 ` fabien at gcc dot gnu.org 2014-02-06 14:22 ` abel at gcc dot gnu.org 2014-02-06 16:20 ` fabien at gcc dot gnu.org 2014-02-07 5:12 ` abel at gcc dot gnu.org 2014-02-08 8:44 ` harald at gigawatt dot nl 2014-02-08 15:57 ` redi at gcc dot gnu.org 2021-01-29 12:22 ` anthonysharp15 at gmail dot com 2021-04-28 18:48 ` anthonysharp15 at gmail dot com
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=20050111170805.17077.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: 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).