public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gdr@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gdr@gcc.gnu.org,
	nobody@gcc.gnu.org, wxy@london.kivera.com
Subject: Re: c++/3935: const static class member access
Date: Mon, 13 Aug 2001 04:27:00 -0000	[thread overview]
Message-ID: <20010813112703.28749.qmail@sourceware.cygnus.com> (raw)

Synopsis: const static class member access

Responsible-Changed-From-To: unassigned->gdr
Responsible-Changed-By: gdr
Responsible-Changed-When: Mon Aug 13 04:27:02 2001
Responsible-Changed-Why:
    Boo!
State-Changed-From-To: open->analyzed
State-Changed-By: gdr
State-Changed-When: Mon Aug 13 04:27:02 2001
State-Changed-Why:
    Strictly speaking, your program is ill-formed since the definitions
    for foo1::left and foo1::right are missing.
    
    That said, I must confess that GCC-3.0 behaviour is a regression over
    2.95, and inconsistent.
    
    -- Gaby

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3935&database=gcc


             reply	other threads:[~2001-08-13  4:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-13  4:27 gdr [this message]
2002-04-12 18:56 mmitchel

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=20010813112703.28749.qmail@sourceware.cygnus.com \
    --to=gdr@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    --cc=wxy@london.kivera.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).