Re: Destroy a Singleton : static or not static ?

From:

James Kanze <james.kanze@gmail.com>

Newsgroups:

comp.lang.c++

Date:

Wed, 17 Feb 2010 12:28:10 -0800 (PST)

Message-ID:

<6af639d0-3a55-4d21-957e-8551fc521fba@d27g2000yqf.googlegroups.com>

On Feb 16, 1:16 pm, "Leigh Johnston" <le...@i42.co.uk> wrote:

"requinham" <requin...@gmail.com> wrote in message

news:b31460c5-db1e-488f-a1fb-1cf1ad2f0d7f@b2g2000yqi.googlegroups.com...

i would know if the conception of singeleton pattern define
the function who destroy the unique instance as static or
not ?

because in the code of global program, this function must be
the latest function executed by the singleton and after that
she will return the handle to the main or another
independant function so it's not necessary to define this
method (destroy()) as static !

Could you be more specific as there are various ways of
implementing a singleton. If you are using the Meyers
Singleton then there is no need for a destroy function static
or otherwise as the singleton is destroyed automatically at
the appropriate time during program termination.

For some definition of "appropriate". Generally, it's
preferrable that a singleton never be destroyed.

--
James Kanze