public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nathan@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/45: Template Specialization Date: Tue, 22 Oct 2002 16:56:00 -0000 [thread overview] Message-ID: <20021022235603.32488.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/45; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: c++/45: Template Specialization Date: Tue, 22 Oct 2002 18:51:23 -0500 (CDT) Someone should re-name this report to "Matching of partial specialization of classes" Here's a redux: ----------------------------------------- template <int N> struct Int {}; template <char C> struct Char{}; template <typename A, typename B> struct X; template <char C, int N> struct X< Char<C>, Int<N> > { typedef Int<C> val; }; template <int N, char C> struct X< Int<N>, Char<C> > { typedef Int<N> val; }; X< Int<0>, Char<'1'> >::val i; ---------------------------------------- In ways I don't understand, this bug goes away if in the declaration of the second partial specialization, "int N" and "char C" is reversed, something that should have absolutely no effect on matching of templates. In some other ways I do not understand either, the problem also goes away if I change the template argument of "Char" from "char" to "int", something that should also not affect matching, but does. Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-10-22 23:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-22 16:56 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-11-20 18:34 Wolfgang Bangerth 2001-11-22 14:16 nathan 2001-11-22 14:16 nathan
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=20021022235603.32488.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nathan@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).