Re: [Dri-devel] __driConfigOptions, __driNConfigOptions

2003-12-08 Thread Felix Kühling
Am 08.12.2003 22:41:40 schrieb(en) Felix Kühling: > > Am 08.12.2003 18:57:14 schrieb(en) Ian Romanick: [snip] > > Felix would be able to answer better, but I believe the reason was so > > that the config utility could load the *_dri.so and get the list of > > options for that driver. > > Preci

Re: [Dri-devel] __driConfigOptions, __driNConfigOptions

2003-12-08 Thread Felix Kühling
Am 08.12.2003 18:57:14 schrieb(en) Ian Romanick: > Keith Whitwell wrote: > > Keith Whitwell wrote: > > > >> Is there any reason why these things are extern references rather than > >> parameters to an initialization function? > >> > >> Basically by making them extern references, it means that th

Re: [Dri-devel] __driConfigOptions, __driNConfigOptions

2003-12-08 Thread Ian Romanick
Keith Whitwell wrote: Keith Whitwell wrote: Is there any reason why these things are extern references rather than parameters to an initialization function? Basically by making them extern references, it means that the files cannot be compiled into a driver which doesn't use them - I guess this

Re: [Dri-devel] __driConfigOptions, __driNConfigOptions

2003-12-08 Thread Keith Whitwell
Keith Whitwell wrote: Is there any reason why these things are extern references rather than parameters to an initialization function? Basically by making them extern references, it means that the files cannot be compiled into a driver which doesn't use them - I guess this is the reason behind

[Dri-devel] __driConfigOptions, __driNConfigOptions

2003-12-08 Thread Keith Whitwell
Is there any reason why these things are extern references rather than parameters to an initialization function? Basically by making them extern references, it means that the files cannot be compiled into a driver which doesn't use them - I guess this is the reason behind the recent rework of c