public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Carlo Wood <carlo@alinoe.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/7468: prototype "doesn't match" a candidate that is actually a perfect match. Date: Fri, 02 Aug 2002 05:26:00 -0000 [thread overview] Message-ID: <20020802122608.7515.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7468; it has been noted by GNATS. From: Carlo Wood <carlo@alinoe.com> To: Gabriel Dos Reis <gdr@integrable-solutions.net> Cc: gcc-gnats@gcc.gnu.org Subject: Re: c++/7468: prototype "doesn't match" a candidate that is actually a perfect match. Date: Fri, 2 Aug 2002 14:20:58 +0200 On Fri, Aug 02, 2002 at 10:55:41AM +0200, Gabriel Dos Reis wrote: > carlo@alinoe.com writes: > > [...] > > | Note that the error goes away > | when either > | 1) the template is removed > | 2) the static const is removed and '4' is put directly in the typedef > | 3) the typedef is replaced by a more normal typedef > | 4) the (foo_t*) is replaced with (foo_t) > | > | Very peculiar bug. > > Indeed. This bug is actually a duplicate of old PRs (I don't have the > id off hand but I do know it is there since :-). I'll close yours and > mention the previous entry. OK? > > -- Gaby Hmm, not really ok unless you are sure it will be fixed. This problem looks a bit like PR 54, but that has been suspended for "years" :/. Besides, it says "it was fixed" (a year ago), so are you SURE this isn't a new bug? -- Carlo Wood <carlo@alinoe.com>
next reply other threads:[~2002-08-02 12:26 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-02 5:26 Carlo Wood [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-28 16:53 bangerth 2002-09-13 16:35 nathan 2002-08-02 6:46 Gabriel Dos Reis 2002-08-02 2:06 Gabriel Dos Reis 2002-08-01 19:56 carlo
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=20020802122608.7515.qmail@sources.redhat.com \ --to=carlo@alinoe.com \ --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).