public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "michal.t at tiscali dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/47861] New: static variables inside member functions
Date: Wed, 23 Feb 2011 16:50:00 -0000 [thread overview]
Message-ID: <bug-47861-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47861
Summary: static variables inside member functions
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Severity: trivial
Priority: P3
Component: c++
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: michal.t@tiscali.it
I know it has been probably discussed several times and probably eons ago.
The language semanthics may induct to assume static variables defined in a
member function are going to be modified only for a specifc class instance -
obviously this is not happening.
Not a c++ bug, a c++ trap.
next reply other threads:[~2011-02-23 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 16:50 michal.t at tiscali dot it [this message]
2011-02-23 17:57 ` [Bug c++/47861] " paolo.carlini at oracle dot com
2011-02-23 20:58 ` michal.tlk at gmail dot com
2011-02-23 21:20 ` redi at gcc dot gnu.org
2011-02-23 21:22 ` redi at gcc dot gnu.org
2011-02-23 21:28 ` pinskia at gcc dot gnu.org
2011-02-23 22:09 ` redi at gcc dot gnu.org
2011-02-24 9:52 ` michal.t at tiscali dot it
2011-02-24 10:57 ` redi at gcc dot gnu.org
2011-02-24 11:20 ` paolo.carlini at oracle dot com
2011-02-24 11:28 ` michal.t at tiscali dot it
2011-02-24 11:34 ` redi at gcc dot gnu.org
2011-02-24 13:13 ` michal.t at tiscali dot it
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=bug-47861-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).