public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bangerth at dealii dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/23227] SFINAE bug Date: Wed, 14 Sep 2005 21:11:00 -0000 [thread overview] Message-ID: <20050914211057.10264.qmail@sourceware.org> (raw) In-Reply-To: <20050804093039.23227.sylvain.pion@sophia.inria.fr> ------- Additional Comments From bangerth at dealii dot org 2005-09-14 21:10 ------- Fair enough. And to get more to the point of only using user-defined conversion sequences (instead of the standard conversion from double to int): -------------------- struct A; struct B { B(const double &); }; void f(const A&) { } void f(const B&) { } void g() { f(2.0); } ---------------------- This is accepted by all compilers I have as well. I retract my point of view. This doesn't mean, however, that I'm convinced that the opposite would be true. W. -- What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23227
next prev parent reply other threads:[~2005-09-14 21:11 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-04 9:30 [Bug c++/23227] New: " sylvain dot pion at sophia dot inria dot fr 2005-08-04 13:07 ` [Bug c++/23227] " pinskia at gcc dot gnu dot org 2005-08-04 13:27 ` gdr at integrable-solutions dot net 2005-08-05 4:02 ` pinskia at gcc dot gnu dot org 2005-09-14 15:35 ` bangerth at dealii dot org 2005-09-14 21:03 ` gdr at integrable-solutions dot net 2005-09-14 21:11 ` bangerth at dealii dot org [this message] 2005-09-14 21:23 ` pinskia at gcc dot gnu dot org 2005-09-14 22:11 ` gdr at integrable-solutions dot net 2005-09-18 19:43 ` fang at csl dot cornell dot edu [not found] <bug-23227-1902@http.gcc.gnu.org/bugzilla/> 2009-02-22 16:29 ` steven at gcc dot gnu dot org 2009-02-22 16:39 ` paolo dot carlini at oracle dot com 2009-03-04 1:28 ` jason at gcc dot gnu dot org 2009-03-04 1:29 ` jason at gcc dot gnu dot org 2009-03-04 1:29 ` jason at gcc dot gnu dot org
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=20050914211057.10264.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).