public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: Paolo Carlini <paolo.carlini@oracle.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [C++ Patch / RFC] PR 50864
Date: Wed, 26 Oct 2011 20:47:00 -0000	[thread overview]
Message-ID: <4EA86CD1.6090507@redhat.com> (raw)
In-Reply-To: <4EA867B7.7050406@oracle.com>

On 10/26/2011 04:04 PM, Paolo Carlini wrote:
> The below tries to catch the problem very early, in
> cp_parser_postfix_dot_deref_expression and apparently works fine, passes
> the testsuite, etc. Is it too early? Is the check tight enough?

At a glance, it looks too early; it's valid to have namespace-qualified 
names after ->.

namespace A
{
   struct B
   {
     int i;
   };
};

A::B* b;
int i = b->A::B::i;

Jason

  reply	other threads:[~2011-10-26 20:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-26 20:31 Paolo Carlini
2011-10-26 20:47 ` Jason Merrill [this message]
2011-10-26 21:05   ` Paolo Carlini
2011-10-26 21:16     ` Paolo Carlini
2011-10-26 22:15       ` Paolo Carlini
2011-11-07 21:52       ` Jason Merrill
2011-11-07 22:06         ` Paolo Carlini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EA86CD1.6090507@redhat.com \
    --to=jason@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=paolo.carlini@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).