Re: [Freeglut-developer] Font binary compatibility

[Stephen J B. <sj...@li...>]

Brian Paul wrote:

> Or, how about defining new FREEGLUT_<fontname> tokens which evaluate to 
> ((void *) aConstant) values like the WIN32 code does now?

Yes - I guess so. (Although I wouldn't use 'FREEGLUT' as the prefix). The
nice thing about that is that at some point in the distant future, when
GLUT-classic is (hopefully) dead and buried, we can quietly change the
header to say:

#define GLUT_BITMAP<whatever>  FREEGLUT_BITMAP<whatever>

...and whilst that would prevent new programs compiled with this header
from running with GLUT, it would mean they were protected from subsequent
breakage under freeglut...and we could still have the old (nasty) code
inside freeglut to maintain binary compatibility with programs compiled
under both older versions of freeglut and GLUT-classic.

This is easy to do - there is only one freeglut function to change.

>  From what I understand the font stuff is OK on WIN32; it's the Unix 
> implementation that's problematic.

Yep - that's correct.  Nate Robins (who did the Windows port of GLUT)
evidently either thought this through or (more likely) ran into the
exact problem we're running into.  Fortunately, he was able to fix
it cleanly because there were no existing Windows GLUT programs to
be compatible with.


----
Steve Baker                      (817)619-2657 (Vox/Vox-Mail)
L3Com/Link Simulation & Training (817)619-2466 (Fax)
Work: sj...@li...           http://www.link.com
Home: sjb...@ai...       http://www.sjbaker.org