Hi All, On 22 June 2012 09:41, Jorge Izquierdo Ciges <[email protected]> wrote: > Yes, we already reported the same bug. We are waiting for Robert to decide > what's best because that code was changed to fix another bug when OSG was > closing.
I'm currently review static usage usage more generally in the OSG, the static's in Scene.cpp are part of this. The problem being that one platform and OSG usage breaks one way and another breaks doing another so in cases like Android breaking with the static change in Scene.cpp it's not a straight forward case of just reverting changes - to do so would fix a problem for one user only to break it for another. Static/singleton's are a useful mechanism for solve a range of problems but come with their own baggage, there may be places in the OSG where we can just remove the use of statics completely, but others we still need them so it's a case of how do we enforce initialization in an appropriate way. In the Scene.cpp case my current preference is to create a single static for the container and the mutex that protects it, and in other places I feel this would be appropriate too, unfortunately there isn't any universal pattern to our static usage to be able to standardize it easily so we it's likely we'll be stuck with individual solutions in different cases. Thanks for your patience, Robert. _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
