public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Artem Khodush" <artem@duma.gov.ru> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org Subject: Re: c++/3028: 3.0 Compiler complains about template that used to work under 2.95 Date: Fri, 01 Jun 2001 08:16:00 -0000 [thread overview] Message-ID: <20010601151601.6832.qmail@sourceware.cygnus.com> (raw) The following reply was made to PR c++/3028; it has been noted by GNATS. From: "Artem Khodush" <artem@duma.gov.ru> To: <peterson@austin.ibm.com> Cc: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org> Subject: Re: c++/3028: 3.0 Compiler complains about template that used to work under 2.95 Date: Fri, 1 Jun 2001 18:58:15 +0400 > > template<class ALLOC> class IListBase > { > protected: > struct IListNode > { > IListNode *next; > int datum; > }; > > class IListNode *head; > class IListNode *tail; > > int find(int datum); > }; > > template<class ALLOC> int IListBase<ALLOC>::find(int d) > { > IListNode<ALLOC> *node; > for(node = head; node != 0; node = node->next) > { > if(node->datum == d) > { > return 1; > } > } > return 0; > } > > > >Fix: > A workaround seems to be to move the inner node class > out of the template list class and make it its own template > (but that breaks the protection). Well, the code works if <ALLOC> after the IListNode is omitted. I believe gcc 3.0 is right, IListNode is indeed not a template.
next reply other threads:[~2001-06-01 8:16 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-06-01 8:16 Artem Khodush [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-06-01 18:26 Gabriel Dos Reis 2001-06-01 18:26 Gabriel Dos Reis 2001-06-01 12:46 Alexandre Oliva 2001-06-01 12:26 James L Peterson 2001-06-01 11:36 Alexandre Oliva 2001-06-01 8:46 James L Peterson 2001-06-01 7:26 peterson
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=20010601151601.6832.qmail@sourceware.cygnus.com \ --to=artem@duma.gov.ru \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).