public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/13616] fails to look up template specialization of template template parameter involving own template parameters
Date: Thu, 08 Jan 2004 18:45:00 -0000	[thread overview]
Message-ID: <20040108184514.30750.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040108163101.13616.hetadres@email.com>


------- Additional Comments From bangerth at dealii dot org  2004-01-08 18:45 -------
Just for completeness, if someone wants to make a testcase for this: 
take this code 
------------------------ 
template<class P> struct O { 
    template<class T> class I { }; 
}; 
 
template <class, template <class> class> struct A; 
template <class P> struct A <P, O<P>::I> {}; 
 
template <class, template <class> class> struct B; 
template <class P> struct B <P, O<P>::template I> {}; 
 
int main() { 
  A<double, O<double>::I> a; 
  B<double, O<double>::I> b; 
} 
------------------------- 
3.3.x accepts the specializations, but whines when declaring "a" 
that we use an incomplete type. It doesn't do so for B, though. 
 
Present mainline doesn't accept the specialization right away. That's 
the correct behavior. 
 
W. 

-- 


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


      parent reply	other threads:[~2004-01-08 18:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-08 16:31 [Bug c++/13616] New: " hetadres at email dot com
2004-01-08 18:21 ` [Bug c++/13616] " pinskia at gcc dot gnu dot org
2004-01-08 18:41 ` bangerth at dealii dot org
2004-01-08 18:45 ` bangerth at dealii dot org [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=20040108184514.30750.qmail@sources.redhat.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).