public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: libstdc++/3738: static member variables are well handled by containers
@ 2001-08-24 1:35 aoliva
0 siblings, 0 replies; 3+ messages in thread
From: aoliva @ 2001-08-24 1:35 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, luca.formaggia, nobody
Synopsis: static member variables are well handled by containers
State-Changed-From-To: feedback->closed
State-Changed-By: aoliva
State-Changed-When: Fri Aug 24 01:35:45 2001
State-Changed-Why:
Not a bug. Even static const data members initialized with a constant must be defined outside the class body.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3738&database=gcc
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: libstdc++/3738: static member variables are well handled by containers
@ 2001-08-20 14:45 pme
0 siblings, 0 replies; 3+ messages in thread
From: pme @ 2001-08-20 14:45 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, luca.formaggia, nobody
Synopsis: static member variables are well handled by containers
State-Changed-From-To: open->feedback
State-Changed-By: pme
State-Changed-When: Mon Aug 20 14:44:58 2001
State-Changed-Why:
The attached file seems to have been lost; at least, I'm
having problems retrieving it from GNATS. (This is not
unsurprising, GNATS can't seem to get MIME quite right.)
Can you send just a plain not_working.cc, rather than a
compressed tar file?
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3738&database=gcc
^ permalink raw reply [flat|nested] 3+ messages in thread
* libstdc++/3738: static member variables are well handled by containers
@ 2001-07-19 12:06 luca.formaggia
0 siblings, 0 replies; 3+ messages in thread
From: luca.formaggia @ 2001-07-19 12:06 UTC (permalink / raw)
To: gcc-gnats
>Number: 3738
>Category: libstdc++
>Synopsis: static member variables are well handled by containers
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Jul 19 12:06:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: luca.formaggia@epfl.ch
>Release: gcc version 3.0
>Organization:
>Environment:
i686-pc-linux-gnu
Linux kernel 2.4.3-12 on intel PIII (i686)
>Description:
Cannot access a public static member of an object A
contained in a stl container<A>
by simply using container[n].static_member (it compiles
but loader gives undefined reference)
It works if I assign A foo=container[n]; and then
foo.static member.
>How-To-Repeat:
just compile with g++ the not_working.cc file.
The working.cc contains the workaround (which
compiles and runs fine).
>Fix:
I do not know (apart the workaround)
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="example.tgz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="example.tgz"
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-08-24 1:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-08-24 1:35 libstdc++/3738: static member variables are well handled by containers aoliva
-- strict thread matches above, loose matches on Subject: below --
2001-08-20 14:45 pme
2001-07-19 12:06 luca.formaggia
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).