This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] Add UNARY_PLUS_EXPR to C++ front-end (take 2)
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Roger Sayle <roger at eyesopen dot com>
- Cc: Mark Mitchell <mark at codesourcery dot com>, <gcc-patches at gcc dot gnu dot org>
- Date: 28 May 2005 04:21:57 +0200
- Subject: Re: [PATCH] Add UNARY_PLUS_EXPR to C++ front-end (take 2)
- References: <Pine.LNX.firstname.lastname@example.org>
Roger Sayle <email@example.com> writes:
| On 28 May 2005, Gabriel Dos Reis wrote:
| > Roger Sayle <firstname.lastname@example.org> writes:
| > Thanks for doind this. The addition of the code should be in
| > pp_cxx_unary_expression, which has the following comments:
| If you look closely, you'll see that this code was added to
| pp_cxx_unary_expression (and even mentioned in the ChangeLog)
| precisely because of the helpful comment you cited. The thing
| that might have been confusing is that because the syntax is:
You're absolutely right: I'm was completely confused in the way I read
the ChangeLog. Please ignore my previous comment (how does one cancel
message sent to you and GCC list? ;))
| >> /* unary-expression:
| >> ...
| >> unary-operator cast-expression
| we now need to call "cast-expression" from "unary-expression".
| As a result, with my change pp_cxx_unary_expression needs to invoke
| pp_cxx_cast_expression, which unfortunately is defined later in the
| source file. As a result, I have to add a new prototype for the
| function pp_cxx_cast_expression even though my functional change
| is to pp_cxx_unary_expression.
| I hope this make sense.
All the way down. Thanks for your patience.