Jon Leech wrote:
>
> I've revised the extension specification (attached) following our
> straw poll to make it a GLX function returning context-independent
> pointers. As a logical consequence the function should return any of GL,
> GLX, or GLU functions.
>
> Hopefully, the nitpicky details of moving it from GL to GLX have
> been taken care of. If there are any actual bugs in the proposal, please
> identify them ASAP. This extension *will* be presented to the ARB on
> Monday, November 8th.
Other than the following comments, I think the spec looks great.
1) It doesn't make sense for glXGetProcAddress to return GLU entrypoints.
glX doesn't even know or care that GLU exists, so it certainly shouldn't
be returning pointers into GLU. If there's an actual need to get
pointers to GLU extensions, we should define a gluGetProcAddress. I
propose that we don't.
2) I don't see any reason why 1.0 core functions shouldn't be queryable
(next to the last issue).
3) A NULL return value should not indicate anything except that something
is wrong (and glError should be checked in that case to find out what
went wrong). NULL certainly shouldn't give any indication as to whether
the queried extension exists or is valid.
4) I don't think it's necessary to specify that "glXGetProcAddress(foo) ==
&foo". In fact, I think it's an implementation detail that may not be
true in all implementations, so it's much better not to constrain the
implementation by mentioning it.
Cheers!
--
Brett Johnson <[EMAIL PROTECTED]>
Workstation Systems Lab
Hewlett-Packard Company
"Politicians, like diapers, should be changed regularly,
and for the same reason."
