Hi JS, On Wed, Jun 17, 2009 at 2:30 PM, Jean-Sébastien Guay<jean-sebastien.g...@cm-labs.com> wrote: >> For the 2.10 release we'll need to do this same check, please don't >> assume I'll remember and test it out yourself to make sure that I >> don't miss anything. > > OK, so I assume the policy I was asking about is: keep the option and > continue to make sure OSG itself compiles cleanly with both settings.
Yes this is the current policy, but it's a little informal. As long as the code base can be easily maintained to work without the implicit casts I'm happy to maintain backwards compatibility. There might be a point in the future that the pain vs gain no longer justifies this - for instance an OSG-3.0 we might just drop this as other sweeping changes would not be backwards compatible anyway. > It should really have been made explicit before, so that all contributors > remember to use .get() when necessary. Now it is, thanks. I'm note quite where little things like this might be made explicit - on the wiki, on mailing lists threds. There are lots of little things that we could potential tie down and formalize, but many things are that cast in stone and evolve, often it's just easier to take things as they come as resolve problems as they arise. Robert. _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
