Re: strange crush when using template singleton class

From:

"SvenC" <SvenC@community.nospam>

Newsgroups:

microsoft.public.vc.atl

Date:

Sun, 18 Mar 2007 13:27:11 +0100

Message-ID:

<ODUXGjVaHHA.3520@TK2MSFTNGP04.phx.gbl>

Hi andrew,

"andrew" <user@earth> wrote in message
news:uZYP7nPaHHA.4940@TK2MSFTNGP05.phx.gbl...

<snip/>

I might got copies of the same object due to the fact that Instance() gets
inlined and I get multiple static variables with internal linkage in the
CPP files where I am calling Instance( ) method.

<snip/>

9 In July 1996, the ?ISO/ANSI standardization committee changed the
default
linkage of inline functions to external, so the problem I describe here
has
been eliminated, at least on paper. Your compilers may not yet be in
accord
with ?the standard, however, so your best bet is still to shy away from
inline functions with static data.

The question is, is 2003 C++ compiler in accord with that standard ?
How can i verify it ?

I don't know how to verify that but you might go for the "best bet ... shy
away" with a little change to your singleton class, by moving obj to class
level scope:

template<class T>
class CSingleton
{
public:
static T* Instance() { return &obj_; }

protected:
CSingleton() {}

private:
static T obj_;

operator=(const CSingleton&);
CSingleton(const CSingleton&);
};

Does that fix your problem?

Bye,
SvenC