Hi Neil, We've had similar submissions in the past by previously I haven't merged due to problems with old compiler not compiling the code -I have even written similar methods myself only to have to remove them later due to compile errors on other systems. Having an optional compile path is a possibility, but it would mean that code that compiles on a modern machine being ported to an older machine could fail as methods it relies upon won't port.
Perhaps developers interested in full portability could use a CMake option to switch on/off the new methods, so be able to spot problem usage under modern systems before they port over to older systems. It would be worth exploring these issues again as well. We no longer support VS 6.0 which was one of the problem child, the other is SunOS compilers and MipsPro, the these later two can handle your code unmodified then we might be able to get away with no optional compile which is by far my preference. W.r.t using of boost smart pointers, this would be possible but the payload is the dependency on boost and the breaking of backwards compatibility, so it might be an interesting academic exercise but isn't one that will be integrated in OSG-2.x. Steps next would be to see how well the proposed code ports onto SunOS compilers and MipsPro. Mathias? Any chance you could try a build on an old IRIX and Sun box? Cheers, Robert. _______________________________________________ osg-submissions mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
