public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: c++/3935: const static class member access
@ 2002-04-12 18:56 mmitchel
  0 siblings, 0 replies; 2+ messages in thread
From: mmitchel @ 2002-04-12 18:56 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, gdr, wxy

Synopsis: const static class member access

State-Changed-From-To: analyzed->closed
State-Changed-By: mmitchel
State-Changed-When: Fri Apr 12 18:56:05 2002
State-Changed-Why:
    Fixed in GCC 3.1.

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: c++/3935: const static class member access
@ 2001-08-13  4:27 gdr
  0 siblings, 0 replies; 2+ messages in thread
From: gdr @ 2001-08-13  4:27 UTC (permalink / raw)
  To: gcc-bugs, gcc-prs, gdr, nobody, wxy

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2002-04-13  1:56 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-12 18:56 c++/3935: const static class member access mmitchel
  -- strict thread matches above, loose matches on Subject: below --
2001-08-13  4:27 gdr

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).