From: Kriang Lerdsuwanakij <lerdsuwa@scf-fs.usc.edu>
To: Andrey Slepuhin <pooh@msu.ru>
Cc: egcs@cygnus.com, Kriang Lerdsuwanakij <lerdsuwa@scf-fs.usc.edu>,
Mark Mitchell <mmitchell@usa.net>
Subject: Re: problems with partial specialization of templates with template parameters
Date: Wed, 18 Feb 1998 14:54:00 -0000 [thread overview]
Message-ID: <Pine.SV4.3.94.980218144946.24324A-100000@lvl-sun674.usc.edu> (raw)
In-Reply-To: <XFMail.980218205626.pooh@msu.ru>
On Wed, 18 Feb 1998, Andrey Slepuhin wrote:
> Hi,
> I have problems with partial specialization of templates
> with template parameters. I.e., trying to compile the following
> example:
> ----------------------------------------------
> template <class T, template <class T> class C>
> struct X
> {};
>
> template <class T>
> struct Y
> {};
>
> template <class T>
> struct Z
> {};
>
> template <class T>
> struct X<T,Y>
> {};
>
> void main()
> {
> X<int,Y> a;
> X<int,Z> b;
> }
> -----------------------------------------------
> I got with egcs-980205:
> -----------------------------------------------
> tmp1.cc:20: sorry, not implemented: use of `template_decl' in template type
> unification
> -----------------------------------------------
> Removing definition of X<T,Y> all works Ok. Also all works, if
> I remove "X<int,Z> b;" line (strange, isn't?). Is something
> really not implemented? Do I use invalid syntax? Or this is
> a bug? Any help is appreciated.
>
> Regards,
> Andrey.
>
>
Thanks for the report. It's a bug. It tries to match X<int,Z> against
X<T,Y> and dies with the error message. I'll post a patch for this.
--Kriang
next prev parent reply other threads:[~1998-02-18 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-02-18 14:54 Andrey Slepuhin
1998-02-18 14:54 ` Kriang Lerdsuwanakij [this message]
1998-02-18 23:56 ` Patch for " Kriang Lerdsuwanakij
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=Pine.SV4.3.94.980218144946.24324A-100000@lvl-sun674.usc.edu \
--to=lerdsuwa@scf-fs.usc.edu \
--cc=egcs@cygnus.com \
--cc=mmitchell@usa.net \
--cc=pooh@msu.ru \
/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).