This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Ping: PATCH to generate error for address of cast
- From: Nathan Sidwell <nathan at codesourcery dot com>
- To: Matt Austern <austern at apple dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 14 Aug 2002 18:54:36 +0100
- Subject: Re: Ping: PATCH to generate error for address of cast
- Organization: Codesourcery LLC
- References: <A217D0EA-AFAB-11D6-8BFC-00039390D9E0@apple.com>
Matt Austern wrote:
> (By the way, you might be wondering why I'm doing all this
> complicated stuff instead of just fixing lvalue_or_else. Answer:
> I found that changing lvalue_or_else breaks the case-as-lvalue
> extension in a couple places. Having a regression test suite is
What are the semantics for cast-is-lvalue extension? (why is &(t)thing
not allowed, but some other lvalue use is ok?)
IMHO It would be better to add another parm to lvalue_or_else, and
fix it there - there may be other places which are erroneously
allowing lvalue casts.
(I bet we can't kill the extension ... )
nathan
--
Dr Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC
'But that's a lie.' - 'Yes it is. What's your point?'
nathan@codesourcery.com : http://www.cs.bris.ac.uk/~nathan/ : nathan@acm.org