But you might! The singleton class pattern isn't synonymous with static configuration. There are other uses for singletons.
I don't really mean singletons are only for configuration ! I just insist that singletons really are singletons; if you want a variation of a singleton locally in your program, that simply means you shouldn't be using a singleton in the first place.
Tell me how do singleton's break encapsulation any more/less than a set of package variables? If you're using them to return static configuration information (as you seem to be proposing) then they encapsulate exactly the same thing.
As I understand it accessing any variable inside another package directly is EVIL :) When using a singleton, you ask the object to provide you with the data (thru a getter/setter or whatever mecanism you're using, anything BUT direct access), you don't simply take it. That's the difference between breaking or not breaking encapsulation.
In reply to Re^13: what is a propper way to make a chunk of data accessible to all my packages for retrieval and modification ?
by wazoox
in thread what is a propper way to make a chunk of data accessible to all my packages for retrieval and modification ?
by leocharre
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |