public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/47861] static variables inside member functions Date: Thu, 24 Feb 2011 10:57:00 -0000 [thread overview] Message-ID: <bug-47861-4-1dRmA2i4pb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47861-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47861 --- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-02-24 10:44:15 UTC --- (In reply to comment #7) > The issue is clearly caused by having > declared static the iterator. So that's a bug, don't do that. > Obviously the same snippet code can be > replaced by a simple for each iterator construct. > As you have mentioned > before - static means static...consider only the implication of a code > written in this way...a > forced definition of the iterator being static > would probably prevent some unprapred c++ users to make similar > mistakes. I don't understand, are you now suggesting the local static should be turned into a static member by the compiler?! Again, please explain what warning you want. So far you've shown some buggy code, but haven't explained how GCC could help prevent users from creating that bug. e.g. foo.cc:4:3: In 'MyClass::next(bool)': foo.cc:4:3: Warning: 'it' is declared as a function-scope static, did you want to use a static member variable? For the record, I would be strongly-opposed to such a warning. There are a million ways to write code that is buggy, the compiler cannot possibly infer what you really wanted to do and suggest how to fix all bugs.
next prev parent reply other threads:[~2011-02-24 10:44 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-23 16:50 [Bug c++/47861] New: " michal.t at tiscali dot it 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 [this message] 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-1dRmA2i4pb@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: linkBe 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).