D
Dave
Hello all,
I have made a class into a singleton by having a static get() method which
returns a pointer to the one-and-only instance. This method creates the
instance on the heap if it hasn't already done so in a prior call.
Constructors are private so that the class may not be instaniated from
outside. As I understand it, this is the standard approach and is nothing
new.
I have no need to ever destroy this singleton and re-create a new one in
it's place, so I have not provided a method for destruction.
My question is: Where in my code, if ever, should the singleton be
deallocated? Is it standard practice to just ignore this memory, or would
it really be more proper to find some way to deallocate it manually upon
app. exit?
Thanks,
Dave
I have made a class into a singleton by having a static get() method which
returns a pointer to the one-and-only instance. This method creates the
instance on the heap if it hasn't already done so in a prior call.
Constructors are private so that the class may not be instaniated from
outside. As I understand it, this is the standard approach and is nothing
new.
I have no need to ever destroy this singleton and re-create a new one in
it's place, so I have not provided a method for destruction.
My question is: Where in my code, if ever, should the singleton be
deallocated? Is it standard practice to just ignore this memory, or would
it really be more proper to find some way to deallocate it manually upon
app. exit?
Thanks,
Dave