public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/396: const int null = 0; Date: Tue, 22 Oct 2002 15:46:00 -0000 [thread overview] Message-ID: <20021022224602.23378.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/396; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: c++/396: const int null = 0; Date: Tue, 22 Oct 2002 17:40:47 -0500 (CDT) I don't actually know what the standard would mandate in this case (conversion from 'const int &' to 'int *'), but this is clearly at least confusing (stripped down and condensed testcase from this report): ----------------------------------- void f(int* pn); struct Foo { static void f(int* pn); }; int main() { const int null = 0; f(0); // ok f(null); // ok Foo::f(0); // ok Foo::f(null); // compile error } ---------------------------------- The compiler only gives an error on the call to Foo::f(), not on ::f(), although they have the same signature. For present CVS and 3.2, the error message is x.cc: In function `int main()': x.cc:14: error: invalid conversion from `int' to `int*' x.cc:14: error: initializing argument 1 of `static void Foo::f(int*)' Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-10-22 22:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-22 15:46 Wolfgang Bangerth [this message] 2002-11-20 18:49 Wolfgang Bangerth
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=20021022224602.23378.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --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).