Hi Robert, >> Well, I knew the fact that boost will not be included in OSG... I was just >> talking about "a" Path structure, not "the boost's path structure". :) > > That's not what you suggested in your first post - you were advocating > doing a typedef to the boosts path structure...
Yes, but as you said it was better not to include, then I changed :) > The osgDB library already has a range of functions for managing file > paths. You could possible wrap these up under a class, but we'd need > to migrate a lot of code that current uses std::string's quite happily > to using its replacement - for instance the plugins would all have to > be converted. This is doable but it's not a trivial amount of work. > The high level functions in osgDB/ReadFile and osgDB/WriteFile could > have both the old std::string and a new osgDB::Path interfaces so is > less of an issue. One would have to have a clear value add for > undertaking this work. > > Robert. > _______________________________________________ > osg-users mailing list > osg-users@lists.openscenegraph.org > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org Alright. I think I'd rather leave the subject for now: it seems I'm the only interested in doing such a modification! Even if separating "path" from "string" may be useful later. Anyway, if I don't do that, I will have more time to spend on osgAudio... Thank you for answering. Sukender PVLE - Lightweight cross-platform game engine - http://pvle.sourceforge.net/ _______________________________________________ osg-users mailing list osg-users@lists.openscenegraph.org http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
