public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: bwood@emc.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: c++/10668: [diagnostic] assigning address of non-static member variable to pointer
Date: Wed, 07 May 2003 21:09:00 -0000	[thread overview]
Message-ID: <20030507210942.12252.qmail@sources.redhat.com> (raw)

Old Synopsis: nested class looks for member variable rather than object
New Synopsis: [diagnostic] assigning address of non-static member variable to pointer

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Wed May  7 21:09:42 2003
State-Changed-Why:
    The compiler is correct. However, the message is confusing:
    it taking the address of c1::i, which is of type int (c1::*).
    This cannot be assigned to a variable of type int*. (NB: why
    does it take the address of a member variable? To take the
    address of a member function, it must always be fully
    specialized, i.e. &X::foo. &foo is not sufficient. Why is it
    here?).
    
    Present 3.4 gives the following message:
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c x.cc
    x.cc: In constructor `c1::c2::c2()':
    x.cc:10: error: `c1::i' is not a member of `c1::c2'
    
    This is not nearly as helpful as icc's message:
    g/x> icc -c x.cc -Xc -ansi
    x.cc(10): error: a nonstatic member reference must be relative to a specific object
          c2() { y = &i; };
    
    W.

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


             reply	other threads:[~2003-05-07 21:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 21:09 bangerth [this message]
2003-05-09 18:58 giovannibajo

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=20030507210942.12252.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=bwood@emc.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).