singleton and other designs
Im facing some design problems when programming my application..
I have a class options (object) that stores all the program options and its unique (only one object of this class). Some other classes depend on it (have to be able to access data inside it).
Now I wonder what is the best approach when designing such programs..
Should I make 'class options' singleton or is it better to store a reference in each class that needs access to its data? (So I would have class &options; within each class )
I dont like passing reference of 'class options' to each class that needs to read data from it.
Which way do you prefer, what are the pros and cons?
Thanks for help