This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: generalized lvalues
- From: "Aaron W. LaFramboise" <aaronavay62 at aaronwl dot com>
- Cc: gcc mailing list <gcc at gcc dot gnu dot org>
- Date: Wed, 24 Nov 2004 21:59:19 -0600
- Subject: Re: generalized lvalues
- References: <8AD5AEEF-3914-11D9-8BD2-000A95BCF344@apple.com>
As a user, while I know its a little too late to be concerned, this
concerns me in that some of the code I may be interested in compiling
with GCC may use this extension. The maintainers of this code may be
unwilling to 'fix' it, and hearing that it breaks GCC may be reason for
them to leave it broken perpetually.
So, from a political perspective, this may not be a good thing, as some
proprietary software developers who are vaguely hostile towards GNU may
use this change in GCC as a way to further lock out non-proprietary
compilers.
I sympathize with the notion that extensions to the standard should be
approached conservatively and with much care. But what about the case
where that extension is widely used and all comparable compilers support
it? Are there any widely-used C compilers out that that _don't_
implement the pointer case of this extension?
Aaron W. LaFramboise