Single instance issue

I've to write a single instance class. there are different methods to
control the single instance of a program. I've tried the following
method

class CSingleton
{
public:
CSingleton& GetInstance(){ static CSingleton s; return s; }

private:
CSingleton(){}
~CSingleton(){}
}


The above code failed to compile in Visual C++ 6.0 but compiled in
Visual C++ 7.1 and Visual C++ Express 2008. CRT (in microsoft concept)
calling the destructor of the class. So that Visual C++ 6.0
compilation error (Failed to access destructor) is correct according
to the concept.

I also tried in Dev C++. It was successful but didn't call the dtor of
the class. Which implementation is correct according to the standard.

Sorry if off-topic to the forum

re: Single instance issue

Sarath wrote:How can you call this method and how would you change its definition if
you did want to call it?
It wouldn't compile with any compiler without the missing semicolon.
Never trust that compiler, it's old and not very standards compliant.

--
Ian Collins.

re: Single instance issue

On Dec 21, 4:49*pm, Ian Collins <ian-n...@hotmail.comwrote:Dear All,
I'm extremely sorry to paste wrong code. Please refer this one.

class CSingle
{
public:
static CSingle& GetInstance(){ static CSingle s; return s; }

private:
CSingle() { cout<<"ctor"; }
~CSingle() { cout<<"dtor"; }
};

Sorry for the incovenience.Please refer this code for my question

Regards,
Sarath

re: Single instance issue

On Dec 21, 3:11 am, Sarath <CSar...@gmail.comwrote:declare your destructor public. No reason to hide it.
So what about the compiler generated copy constructor?

int main()
{
CSingle instance;
CSingle copy(instance);
}

and assignment? etc...

re: Single instance issue

On Dec 21, 5:41 pm, Salt_Peter <pj_h...@yahoo.comwrote:It will work if I make the dtor public. But I just want to know about
the destruction of static objects in the above scenario. As All
compilers behaves in different manner.

Regards,
Sarath

re: Single instance issue

On Dec 21, 9:41 am, Salt_Peter <pj_h...@yahoo.comwrote:There's also no reason to make it public, since the code should
work if the destructor is private as well. (A long time ago,
this was a frequent error, since the pre-standard specification
wasn't too clear as to where access of the destructor should be
checked. But any modern compiler should get it right.)
Good point.
Assignment would require two instances, or... Making it private
certainly doesn't hurt, however, and IMHO makes the intent
clearer.

--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France, +33 (0)1 30 23 00 34