public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/45082] Static const signed int class member causes undefined symbol. Date: Mon, 26 Jul 2010 16:33:00 -0000 [thread overview] Message-ID: <20100726163250.16422.qmail@sourceware.org> (raw) In-Reply-To: <bug-45082-19484@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from redi at gcc dot gnu dot org 2010-07-26 16:32 ------- (In reply to comment #2) > The bug/feature may be that re-typing BUFF_SIZE to static const unsigned int > allows the compiler to not report a problem. You're not "re-typing" it, you're providing a definition for a variable that was previously only declared, not defined. > It doesn't require a const > unsigned myclass::BUFF_SIZE; anywhere Yes it does, it requires it where you bind a reference to the variable. If you only want it to be used as an integral constant, don't use it in a context that requires a variable (e.g. reference binding) > and still compiles when it shouldn't. There are dozens of (invalid) bug reports in bugzilla about this, feel free to search for more details. The compiler must not reject your program as it doesn't know until link time that you've failed to define the symbol. It could be defined in some other object or library that you link to later. The bug was in your program, not the compiler. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45082
next prev parent reply other threads:[~2010-07-26 16:33 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-26 15:25 [Bug c++/45082] New: " rwitmer at xmission dot com 2010-07-26 15:32 ` [Bug c++/45082] " jakub at gcc dot gnu dot org 2010-07-26 15:59 ` rwitmer at xmission dot com 2010-07-26 16:33 ` redi at gcc dot gnu dot org [this message] 2010-07-26 16:37 ` redi at gcc dot gnu dot org 2010-07-27 15:27 ` rwitmer at xmission dot com 2010-07-27 23:55 ` redi at gcc dot gnu dot org
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=20100726163250.16422.qmail@sourceware.org \ --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).