Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c++ > #8388

Re: singleton design

Show all headers | View raw

asit <lipun4u@gmail.com> writes:

> I want to design a singleton class. 

Ick. Please reconsider.

There is usually no good reason to enforce that there is only one
instance of a class. Modelling-wise it might make sense to only
actually create one instance, but using the singleton (anti-)pattern
tends to bite you if you want to test either the class itself or
classes depending on it.

> here the rule is to make the constructor private. That's okey. What
> about copy constructor and assignment operator. If I make it
> private, certain things like copying and assigning will lead to
> compiler error. How can I handle them ??

If you want to only have one copy, you don't want to have assignment
or copying creating more than one instance. If the object is immutable,
it might not make any difference, but it still prevents it from being
a singleton. 
You should only pass the object around by reference or pointer.

/L
-- 
Lasse Reichstein Holst Nielsen
 DHTML Death Colors: <URL:http://www.infimum.dk/HTML/rasterTriangleDOM.html>
  'Faith without judgement merely degrades the spirit divine.'

Back to comp.lang.c++ | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

singleton design asit <lipun4u@gmail.com> - 2011-07-31 13:22 -0700
  Re: singleton design Dombo <dombo@disposable.invalid> - 2011-07-31 22:29 +0200
  Re: singleton design Lasse Reichstein Nielsen <lrn.unread@gmail.com> - 2011-08-01 18:39 +0200

csiph-web