public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Nathanael Nerode <neroden@twcny.rr.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/4205 Date: Fri, 03 Jan 2003 12:16:00 -0000 [thread overview] Message-ID: <20030103121606.17260.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/4205; it has been noted by GNATS. From: Nathanael Nerode <neroden@twcny.rr.com> To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, Jens.Maurer@gmx.net, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c++/4205 Date: Fri, 3 Jan 2003 07:07:54 -0500 This has a further perverse piece of behavior not noted before: the following code will, correctly, give an error! -- template<typename F> void quirk(F f) { (*f) (1); } // void foo(int i, int j = 5){} void bar(int i, int j) {} int main() { // quirk(&foo); quirk(&bar); } -- And so will this: -- template<typename F> void quirk(F f) { (*f) (1); } void foo(int i, int j = 5){} void bar(int i, int j) {} int main() { quirk(&bar); quirk(&foo); } -- As long as "foo" is seen *first*, it 'immunizes' all subsequent functions. But not otherwise. This is really bad behavior. It may possibly be related to c++/3784, which has similar "first one seen controls everyone else" behavior, though I doubt it.
reply other threads:[~2003-01-03 12:16 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=20030103121606.17260.qmail@sources.redhat.com \ --to=neroden@twcny.rr.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).