Dear users,
While I fully appreciate that a large scale removal of singletons that appear not to have defects is undesirable. I would like to put forward various references that explain why the singleton pattern is now considered by many (most?) software engineers to be an anti-pattern. http://accu.org/index.php/journals/337 http://code.google.com/p/google-singleton-detector/wiki/WhySingletonsAre Controversial http://blogs.msdn.com/scottdensmore/archive/2004/05/25/140827.aspx I hope this helps provide a balanced view of the singleton approach. Tanguy has excellent reasons for making his suggestion. He is not (and was not attempting to suggest) that he was stating something new. Experience collected from numerous organisations on the singleton pattern has objectively and measurably shown it to be prone to defects due to hidden associations, and causes increased maintenance time when the multiplicity of associations changes. I am not suggesting that singletons must or even should be removed from OSG. The defect counts per module would help in making those sort of decisions. I am suggesting that it's good to look at the above links and incorporate this information into future design decisions and defect resolutions. I hope this helps, Neil Groves
_______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
