On Mon, May 22, 2000 at 08:26:30AM -0500, Stephen J Baker wrote:
| On Fri, 19 May 2000 [EMAIL PROTECTED] wrote:
| > However, I acknowledge that the suggestion is weak, because things in
| > addition to prototypes are involved. How about GL_GLEXT_LEGACY
| > instead? That should capture the notion of restoring all the old
| > behavior.
|
| So is there now some kind of a token that programs can use to say:
|
| #ifdef {something}
| use new ABI-like extension mechanism
| #else
| use legacy mechanisms
| #endif
At first blush, I'd say "use GL_GLEXT_LEGACY for that." (If it's
defined, use the old mechanism; otherwise use the new.) I might have
misunderstood your question, though.
| ...if there is a way to do that with existing tokens (eg by checking
| for the GetProcAddress extension token), then I think it would be wise
| to state what that is in the specification so that people don't invent
| new mechanisms that might be problematic in the future.
Agreed.
Allen
