On Sat, 12 Feb 2000, Bernd Kreimeier wrote:
> GLenum (at least the Mesa version) maps multiple enum names
> to the same value, e.g.
>
> GL_TEXTURE_INTERNAL_FORMAT, GL_TEXTURE_COMPONENTS
> GL_TRUE, GL_NONE, GL_ONE
> GL_FALSE, GL_ZERO,
> GL_LOGIC_OP, GL_INDEX_LOGIC_OP
>
> It's a bit of a nuisance for the GLTrace-like composable
> QGL pipeline I am working on (spits out valid GL code
> where possible, for convenient posting and testing).
>
> Is there a good reason for this duplication. Just accidents
> now protected by virtue of legacy?
At least some of those are cast in stone. You see a LOT
of programs use 'false', 'FALSE' or '0' in place of GL_FALSE
and GL_ZERO. You'd break a lot of code if you split those
apart since one or other of them would end up being non-zero.
Admittedly, the programs that would break would be guilty
of bad coding style - but there are likely to be *so* many
of them that this would be an incredibly disruptive change.
Steve Baker (817)619-2657 (Vox/Vox-Mail)
Raytheon Systems Inc. (817)619-2466 (Fax)
Work: [EMAIL PROTECTED] http://www.hti.com
Home: [EMAIL PROTECTED] http://web2.airmail.net/sjbaker1
