initialize static members

Why doesn't c++ let me initialize static members like this:

class MySound
{
static CSoundManager* g_pSoundManager = NULL;
};

re: initialize static members

bob@coolgroups.com wrote:[color=blue]
> Why doesn't c++ let me initialize static members like this:
>
> class MySound
> {
> static CSoundManager* g_pSoundManager = NULL;
> };[/color]

Because it's prohibited by the Standard. Did you expect any other
answer? Do you want to know why it's that way in the Standard?
You need to ask in comp.std.c++, they discuss _rationales_ behind
the language features. Here you'll just find complaints about the
complexity or inconsistencies in the language.

V
--
Please remove capital As from my address when replying by mail

re: initialize static members

bob wrote:
[color=blue]
> Why doesn't c++ let me initialize static members like this:
>
> class MySound
> {
> static CSoundManager* g_pSoundManager = NULL;
> };[/color]

Because every data item that exists outside of a function must exist in only
one translation unit. "Exist" means the item's binary image (here containing
NULL) resides in the translation unit's object file. The linker wants to
rapidly and efficiently push each item it finds into the output file without
worrying about what other object files might also declare the same item.

Without these rules, the linker would see the binary image of
g_pSoundManager, with its precious NULL, in every object file whose
translation unit #included any header containing MySound. Then it would need
to declare one image "the winner", put it into the output binary, and throw
away all the others. That would waste precious nanoseconds of linker time.
So we must waste minutes (or more) writing lots of stuff twice, once in a .h
file and again in a .cpp file.

If that item were constant, you could initialize it in-situ. That's because
the linker _does_ see many copies in many object files, then declares one
the "winner", then optimizes the others away. That optimization allows
constant abuse, such as via using const_cast<> to change a constant value,
to cause undefined behavior. The optimizations might not see the new value.

(Also try sm_ for static member, not g_ for global.)

--
Phlip
http://www.greencheese.org/ZeekLand <-- NOT a blog!!!

re: initialize static members

anyway, a const static membert can be initialized that way, so
class MySound
{
const static int a = 0;
};

re: initialize static members

bonczz@gmail.com wrote:[color=blue]
> anyway, a const static membert can be initialized that way, so
> class MySound
> {
> const static int a = 0;
> };[/color]

Yes. And not just 'int', but also a 'short', a 'char', a 'long',
a 'bool', a 'wchar_t', and unsigned equivalents. But I think you
need to specify 'static' first. But I can be mistaken.

V
--
Please remove capital As from my address when replying by mail