This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/11427] Problem with conditional expressions as l-values
- From: "jsm at polyomino dot org dot uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Jul 2003 01:53:34 -0000
- Subject: [Bug c/11427] Problem with conditional expressions as l-values
- References: <20030703193348.11427.bonet@cs.ucla.edu>
- Reply-to: gcc-bugzilla at gcc dot gnu dot 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=11427
------- Additional Comments From jsm at polyomino dot org dot uk 2003-07-06 01:53 -------
Subject: Re: Problem with conditional expressions as l-values
On Sun, 6 Jul 2003, falk dot hueffner at student dot uni-tuebingen dot de wrote:
> Maybe we should go the easy way and deprecate it along with casts as
> lvalues, since it seems like a pretty useless extension. (It's not an
> extension in C++, though.)
I'll agree with deprecating all the extended lvalues - including ones such
as this that are valid in C++ - rather than fixing this case of the
extension, whether or not it turns out that the patch introducing this
problem was my C99 non-lvalue arrays patch
<http://gcc.gnu.org/ml/gcc-patches/2001-11/msg00319.html> (just a guess,
that patch removed an "optimization" that passed component references
inside conditional expressions, in order to get correctness for standard
code).