public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mark@codesourcery.com,
	nobody@gcc.gnu.org, oldham@codesourcery.com
Subject: Re: c++/9851: [3.4 regression] confusing error message when using '.', not '->'
Date: Wed, 26 Feb 2003 17:14:00 -0000	[thread overview]
Message-ID: <20030226171434.11151.qmail@sources.redhat.com> (raw)

Old Synopsis: confusing error message when using '.', not '->'
New Synopsis: [3.4 regression] confusing error message when using '.', not '->'

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Wed Feb 26 17:14:33 2003
State-Changed-Why:
    Confirmed. Not very helpful. For reference (so that one
    does not have to open the attachment): code is
    -----------------------
    struct goo {
      void do_nothing () {};
    };
    
    struct foo {
      foo () { g_.do_nothing (); }
      goo * g_;
    };
    ---------------------
    and we get
    
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc
    x.cc: In constructor `foo::foo()':
    x.cc:6: error: expected type-name
    x.cc:6: error: expected `::'
    x.cc:6: error: expected `~'
    x.cc:6: error: expected identifier
    
    This can be considered a regression, since previously
    we got this:
    g/x> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -c x.cc
    x.cc: In constructor `foo::foo()':
    x.cc:6: error: request for member `do_nothing' in `this->foo::g_', which is of
       non-aggregate type `goo*'

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9851


             reply	other threads:[~2003-02-26 17:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-26 17:14 bangerth [this message]
2003-05-04 23:56 Giovanni Bajo

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=20030226171434.11151.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    --cc=nobody@gcc.gnu.org \
    --cc=oldham@codesourcery.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).