Hi Robert,
One concern I've had since we started these discussions on osg/glu/** is
that you stated in your first e-mail on osg-users ("[osg-users] GLU
integration") that you kept the directory/file structure identical to
Mesa so that you could easily merge in any upstream changes they make in
the future. All the changes you make to the files themselves go against
that goal, don't they?
I don't know if it's at all possible, but one approach you could have
used would have been to have a separate "mesa compatibility" header that
you'd include at the top of these files, and in which you'd have
#defines and declarations that would make the code work as-is. That way
when merging a future version of the same code from Mesa you'd see that
the only change to the actual files is the header at the top, all other
differences would be changes Mesa made so would be merged in as-is.
Just a thought, as I said it might not even be possible and it increases
complexity (probably a lot) but at least it preserves the goal of being
able to update the code later. If that's not an important goal after all
(or a less important goal than code clarity, which is probably the case)
then just ignore this idea... :-)
J-S
--
______________________________________________________
Jean-Sebastien Guay [email protected]
http://www.cm-labs.com/
http://whitestar02.webhop.org/
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
