public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Giovanni Bajo" <giovannibajo@libero.it> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/8858: [2003-01-22] Gcc "rebinds" template member names. Date: Fri, 24 Jan 2003 22:56:00 -0000 [thread overview] Message-ID: <20030124225601.32197.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/8858; it has been noted by GNATS. From: "Giovanni Bajo" <giovannibajo@libero.it> To: <gcc-gnats@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <nobody@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>, <eivuokko@bonumit.com> Cc: Subject: Re: c++/8858: [2003-01-22] Gcc "rebinds" template member names. Date: Fri, 24 Jan 2003 23:51:58 +0100 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p r=8858 It seems like the parser is confused by the long chain, and just "ignores" any add<> but the last one: basically, it parses any add<> like it was list::add, instead of list::add::add. In the snippet, the first add<char> is like "overwritten" by the second add<int>, so that the final type is cons<int, cons<double, float> >, as the assert shows. If you just break the chain: typedef list<cons<double,float> >::add<char>::type temp; typedef list<temp>::add<int>::type test_type; everything works as expected (g++ 3.2) Giovanni Bajo
reply other threads:[~2003-01-24 22:56 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030124225601.32197.qmail@sources.redhat.com \ --to=giovannibajo@libero.it \ --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).