Jon Leech wrote:
>
> On Thu, Nov 04, 1999 at 11:47:57AM -0800, John M. Zulauf wrote:
> > > In general, undefined. Since we can now query *any* entry point, and
> > > since error semantics are different for GL, GLX, and GLU entry points,
> > > the only meaningful consistent (e.g. specifiable) behavior you could
> > > require is "termination" or "noop". I don't think "noop" is useful to
> > > the ISV;
> >
> > with context independance, since you cannot know what FUTURE contexts will
> > be created, you must return a non-NULL dispatcher proc. The only open
> > question is whether an unsupported EXT should be dispatched to a noop or
> > error-generating function.
>
> We cannot know what future contexts will be created, but we can know
> the bounded set of all extensions available to the implementation. This
> can be interpreted to mean that all loadable driver modules which may
> ever be used during the current invocation of the X server must be known
> to the server so that it can request this information from all of them
> (mechanism TBD of course).
John, I agree that it is possible to come up with a mechanism to find all
possible 3d drivers, then query them to determine which extensions they
support. But it seems like a lot of work to me, and I don't see any reason
to do it. What is your reasoning for wanting a NULL pointer to indicate
that "no currently available driver supports this extension"?
Cheers!
--
Brett Johnson <[EMAIL PROTECTED]>
Workstation Systems Lab
Hewlett-Packard Company
"Politicians, like diapers, should be changed regularly,
and for the same reason."
