public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "greifel at megatop200 dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/29188] undocumented extension with ambiguous between conversion function/constructor. related to const Date: Sat, 23 Sep 2006 16:29:00 -0000 [thread overview] Message-ID: <20060923162901.27453.qmail@sourceware.org> (raw) In-Reply-To: <bug-29188-13286@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from greifel at megatop200 dot com 2006-09-23 16:29 ------- According to 1.4/8 implementations with extensions are required to "diagnose programs that use extensions that are ill-formed according to this International Standard." This code is ill-formed so presumably g++ should print a warning. I don't know the motivation for the extension but would highlight the question of whether it was intentional that it affects non-const arguments but not const. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29188
next prev parent reply other threads:[~2006-09-23 16:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-09-22 23:46 [Bug c++/29188] New: accepts-invalid " greifel at megatop200 dot com 2006-09-22 23:58 ` [Bug c++/29188] undocumented extension with " pinskia at gcc dot gnu dot org 2006-09-23 16:29 ` greifel at megatop200 dot com [this message] 2006-10-10 3:45 ` bangerth at dealii 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=20060923162901.27453.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).