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: Wed, 23 Feb 2011 22:09:00 -0000	[thread overview]
Message-ID: <bug-47861-4-oHiHnws4AN@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 #6 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-02-23 21:28:10 UTC ---
(In reply to comment #5)
> Also it is hard to produce a warning when it comes to a failure that will only
> be diagnostic at link time.

IIUC I think the OP wants a warning for:

struct S {
  int f();
};

int S::f() {
  static int i = 0;
  return ++i;
}

which doesn't require a definition and can't produce a linker error.  I think
adding a warning for this is silly.


  parent reply	other threads:[~2011-02-23 21:28 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 [this message]
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-oHiHnws4AN@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).