Jon Leech writes:
> P.S. And for those of you who like to bitch about the ARB, you have been
> having a personal introduction via oglbase to the same combination of
> overwork, apathy, self-interest, and argumentativeness that affects the
> speed at which all standards bodies operate.
You forget untimely requests :-).
I have one borderline [sic] ABI issue left. With portability
and backwards compatibility in mind, it's more of an inquiry.
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?
b.
