public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "falk dot hueffner at student dot uni-tuebingen dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/12877] conditional as lvalue gives wrong warning Date: Sun, 02 Nov 2003 21:36:00 -0000 [thread overview] Message-ID: <20031102213631.15814.qmail@sources.redhat.com> (raw) In-Reply-To: <20031102182114.12877.falk@debian.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12877 ------- Additional Comments From falk dot hueffner at student dot uni-tuebingen dot de 2003-11-02 21:36 ------- Subject: Re: conditional as lvalue gives wrong warning "jsm at polyomino dot org dot uk" <gcc-bugzilla@gcc.gnu.org> writes: > > But it's a conditional, not a cast, and I think this extension isn't > > deprecated. > > The cast is implicit; the semantics of conditional expressions mean that > the chars are converted to a common type of int before the conditional > expression is applied to them. Well, as a technical term, casts are always explicit; what happens is a conversion. So IMHO the message is still wrong. > Essentially, the extension in question wasn't properly thought out > for anything other than the case of a common type that is unaffected > by the integer promotions. The problem is arguably that we don't > get a hard error here. C++ has deal with it, so if we really wanted to, it should be possible to come up with sensible semantics. > This extension only isn't deprecated *yet* so that the deprecations > (and any associated problems) could be dealt with one at a time. PR > 11427 has a specific suggestion that it be deprecated and no > objections thereto. I'm inclined on that basis to go ahead with > deprecating conditional expressions as lvalues in C for 3.4, and > then follow with compound expressions, also for 3.4. I agree.
next prev parent reply other threads:[~2003-11-02 21:36 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-11-02 18:21 [Bug c/12877] New: " falk at debian dot org 2003-11-02 21:10 ` [Bug c/12877] " jsm at polyomino dot org dot uk 2003-11-02 21:36 ` falk dot hueffner at student dot uni-tuebingen dot de [this message] 2003-11-05 4:25 ` pinskia at gcc dot gnu dot org 2003-11-09 2:06 ` pinskia at gcc dot gnu dot org 2003-12-21 23:58 ` pinskia at gcc dot gnu dot org 2004-01-23 3:46 ` pinskia 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=20031102213631.15814.qmail@sources.redhat.com \ --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).