On Tue, 9 May 2000 [EMAIL PROTECTED] wrote:
> On Tue, May 09, 2000 at 07:17:59AM -0500, Stephen J Baker wrote:
> |
> | This seems even less acceptable than the original proposal since before, even
> | when "new behavior" was the default ('C'), the implementation was free to export
> | function prototypes for locally valid extensions.
>
> That would make it impossible to check for naked references to
> extension functions at compile time, with the highly unpleasant
> side-effect that an app could fail at startup (because not all
> libGL.so implementations contain entry points for the extension
> functions that the app references).
It's not exactly difficult to find those naked references - a
well-phrased 'grep' will get them all...and it's not like this
is something you'll do by accident. This seems a very tiny
benefit. Once people are writing ABI-compliant programs routinely,
I doubt they'll even *think* of calling a naked extension function
anymore.
> I think it's worthwhile to design oglbase so that this problem can't
> occur. That's one of the reasons why the current proposals are
> structured as they are.
Seems pretty worthless to me - but I guess opinions vary.
Steve Baker (817)619-2657 (Vox/Vox-Mail)
L3Com/Link Simulation & Training (817)619-2466 (Fax)
Work: [EMAIL PROTECTED] http://www.hti.com
Home: [EMAIL PROTECTED] http://web2.airmail.net/sjbaker1
