public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ajrobb57 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53810] template class static not defined
Date: Sat, 30 Jun 2012 06:23:00 -0000	[thread overview]
Message-ID: <bug-53810-4-ezhgM33VaN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53810-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53810

--- Comment #3 from Andrew Robb <ajrobb57 at gmail dot com> 2012-06-30 06:23:28 UTC ---
template<  int n>
class Class {
public:
   static int const _n = n;



I thought that _n was defined.



On 29/06/2012 23:01, pinskia at gcc dot gnu.org wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53810
>
> --- Comment #2 from Andrew Pinski<pinskia at gcc dot gnu.org>  2012-06-29 22:01:07 UTC ---
> GCC is having the correct behavior.  You don't have a definition for the static
> const class variable, only the declaration.  You need the definition as you
> implictly take the address of the variable (via a reference).
>


  parent reply	other threads:[~2012-06-30  6:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 20:31 [Bug c++/53810] New: " ajrobb57 at gmail dot com
2012-06-29 20:41 ` [Bug c++/53810] " ajrobb57 at gmail dot com
2012-06-29 22:01 ` pinskia at gcc dot gnu.org
2012-06-30  6:23 ` ajrobb57 at gmail dot com [this message]
2012-06-30  9:57 ` paolo.carlini at oracle dot com
2012-07-02 10:09 ` redi at gcc dot gnu.org
2012-07-02 12:45 ` ajrobb57 at gmail dot com
2012-07-02 13:38 ` redi at gcc dot gnu.org
2012-07-02 13:41 ` ajrobb57 at gmail dot com

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-53810-4-ezhgM33VaN@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).