This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [C++ PATCH] Change order of tentative parsing in cp_parser_postfix_dot_deref_expression (PR c++/35138)
- From: "Manuel López-Ibáñez" <lopezibanez at gmail dot com>
- To: "Jakub Jelinek" <jakub at redhat dot com>
- Cc: "Mark Mitchell" <mark at codesourcery dot com>, "Jason Merrill" <jason at redhat dot com>, gcc-patches at gcc dot gnu dot org
- Date: Tue, 12 Feb 2008 19:07:18 +0100
- Subject: Re: [C++ PATCH] Change order of tentative parsing in cp_parser_postfix_dot_deref_expression (PR c++/35138)
- References: <20080212175402.GG24887@devserv.devel.redhat.com>
On 12/02/2008, Jakub Jelinek <jakub@redhat.com> wrote:
> Hi!
>
> To fix PR32384, I have changed 3 months ago
> cp_parser_postfix_dot_deref_expression, if postfix-expression is dependent,
> to parse it tentatively as pseudo-dtor first and if that fails do what it
> did before, parse as id-expression. Unfortunately it turns out that even
> tentative parsing isn't silent and sometimes emits errors unconditionally,
> and limiting the PR20293 errors to definitive parse or when committed to
> tentative parse resulted in many regressions.
Can't cp_parser_pseudo_destructor_name parse the expression without
checking types (perhaps even without lookup invocation) and if there
is no CPP_COMPL token return immediately? Am I missing a case here?
Cheers,
Manuel.