static data member lost?

[JustSomeGuy]

I have a class that has a public data member.
If however I declare that data member as being static, then the linker
fails and says the symbol is undefined.
Must static data members be private?

[Victor Bazarov]

JustSomeGuy wrote:

I have a class that has a public data member.
If however I declare that data member as being static, then the linker
fails and says the symbol is undefined.
Must static data members be private?

No. But static data members have to be _defined_ at the namespace level.

V

[JustSomeGuy]

Victor Bazarov wrote:

JustSomeGuy wrote:

I have a class that has a public data member.
If however I declare that data member as being static, then the linker
fails and says the symbol is undefined.
Must static data members be private?

No. But static data members have to be _defined_ at the namespace level.

V

Ok I think I see...

so if I have a class
class myclass
{
public:
static int x;
};

main()
{
myclass c;
cout << std::c.x;
}
Is that correct?

[Victor Bazarov]

JustSomeGuy wrote:

Victor Bazarov wrote:

JustSomeGuy wrote:

I have a class that has a public data member.
If however I declare that data member as being static, then the linker
fails and says the symbol is undefined.
Must static data members be private?

No. But static data members have to be _defined_ at the namespace level.

V

Ok I think I see...

so if I have a class
class myclass
{
public:
static int x;
};

main()
{
myclass c;
cout << std::c.x;
}
Is that correct?

No. First of all, myclass::x is still not defined anywhere. Second,
what's "std::c.x"? Why is 'c' prefixed with 'std::'? Your object is
not in the 'std' namespace, is it? Third, 'cout' is undefined. Did
you forget to include <iostream>, maybe? Fourth, 'main' is a function,
every function needs a return value type: "int main()".

To define myclass::x you need to add this line:

int myclass::x;

somewhere in the same namespace where 'myclass' is defined.

V

[Richard Herring]

In message <cl**********@news.u-bordeaux.fr>, Kante Mamadou Moustapha
<mk****@emi.u-bordeaux.fr> writes

Mike Wahler a écrit :

"JustSomeGuy" <No***@ucalgary.ca> wrote in message
news:41***************@ucalgary.ca...

Victor Bazarov wrote:
JustSomeGuy wrote:

>I have a class that has a public data member.
>If however I declare that data member as being static, then the linker
>fails and says the symbol is undefined.
>Must static data members be private?

No. But static data members have to be _defined_ at the namespace level.

V

Ok I think I see...

No, I don't think you do. See below.

so if I have a class
class myclass
{
public:
static int x;
};

main()
{
myclass c;
cout << std::c.x;
}
Is that correct?

No. Did you even try to compile that? It contains several errors.
#include <iostream>
class myclass
{
public:
static int x;
};
int myclass::x;
int main()
{
std::cout << myclass::x << '\n'; /* prints 0 */
return 0;
}
-Mike

and he should initialize it before using,

No need. Since it's static, it gets initialised.
yes you can say compiler do it, but not sure,
You may not be sure, but the standard is: "The storage for objects with
static storage duration (3.7.1) shall be zero-initialized (8.5) before
any other initialization takes place." (3.6.2/1)
normalization say nothing about that, it depends on the compiler.

???

--
Richard Herring

[Mike Wahler]

"Kante Mamadou Moustapha" <mk****@emi.u-bordeaux.fr> wrote in message
news:cl**********@news.u-bordeaux.fr...

Mike Wahler a écrit :

"JustSomeGuy" <No***@ucalgary.ca> wrote in message
news:41***************@ucalgary.ca...

Victor Bazarov wrote:
JustSomeGuy wrote:

>I have a class that has a public data member.
>If however I declare that data member as being static, then the linker
>fails and says the symbol is undefined.
>Must static data members be private?

No. But static data members have to be _defined_ at the namespace
level.

V

Ok I think I see...

No, I don't think you do. See below.

so if I have a class
class myclass
{
public:
static int x;
};

main()
{
myclass c;
cout << std::c.x;
}
Is that correct?

No. Did you even try to compile that? It contains several errors.
#include <iostream>

class myclass
{
public:
static int x;
};

int myclass::x;

int main()
{
std::cout << myclass::x << '\n'; /* prints 0 */
return 0;
}

-Mike

and he should initialize it before using,

Only if an initial value of zero is not acceptable.
yes you can say compiler do
it,
Yes, the language standard requires that it be initialized to
zero.
but not sure, normalization say nothing about that,
The ISO standard does, in no uncertain terms.
it depends on
the compiler.

Yes, it depends upon whether the compiler's behavior
conforms to the standard. If it does, the object will
be zero-initialized. Always.

-Mike