overriding things for testing, tweaking configuration based on the context, etc. all become much harder than if I'd passed in my own configuration object
Well if you want to change your configuration depending upon the context, then of course you don't want a singleton... which is all about never changing (or overriding) anything wherever you are. Of course it's globals in disguise, but it's globals on steroids too, because you can share your globals across packages as needed :)
In reply to Re^9: 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: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |