public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jbeulich at novell dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/15260] New: base class typedef referred through 'using' declaration still unusable without qualification
Date: Mon, 03 May 2004 10:24:00 -0000	[thread overview]
Message-ID: <20040503102428.15260.jbeulich@novell.com> (raw)

template<typename T> class n;

template<typename T> class b {
protected:
	typedef n<T> n_t;
};

template<typename T> class d : private b<T> {
	using typename b<T>::n_t;
public:
	n_t*test0();
	typename n_t*test1();
	typename b<T>::n_t*test2();
};

void test() {
	d<int> di;
	di.test0();
	di.test1();
	di.test2();
}

results in errors on the unqualified uses of n_t in class d. I cannot see
anything invalid with these constructs, nor can Intel's or a couple of other
compilers I tried this with.

-- 
           Summary: base class typedef referred through 'using' declaration
                    still unusable without qualification
           Product: gcc
           Version: 3.4.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: jbeulich at novell dot com
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: i686-suse-linux
  GCC host triplet: i686-suse-linux
GCC target triplet: i686-suse-linux


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


             reply	other threads:[~2004-05-03 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03 10:24 jbeulich at novell dot com [this message]
2004-05-03 11:20 ` [Bug c++/15260] " pinskia at gcc dot gnu dot org
2005-08-31 21:07 ` redi 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=20040503102428.15260.jbeulich@novell.com \
    --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).