On Thu, Feb 12, 2009 at 5:23 PM, J.P. Delport <[email protected]> wrote: > I'm not arguing about the general evilness/goodness of singletons... I think > the concern is not just about different platforms, but about different > contexts and use cases. It seems like OSG is now being used in new contexts, > e.g. plugins or multiple DLLs like Tanguy mentioned. This is a good thing > IMHO. > > The singleton concerns should be addressed for these specific cases or with > specific questions (or like you suggested with examples or tests). E.g. (a > question I had to address with one of our libraries some time ago): > > How do I, _without_ restarting the process, get the library into the state > it was when I first started the process?
This is a very good question to pose. Rather than discussion pros and cons of what solutions you use, first one needs to pos the right questions about the problems you are trying to tackle, and the problems that you are encountering. In this case I don't have an concrete suggestions about a solution for how to reset OSG related application state. Something to chew over. In the context of 3.0 I'd suggest putting one the goals as being to handle one of these problem domains that the OSG makes awkward to handle right now. Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
