Re: AL 1.1 headers & Linux

Garin Hiebert wrote:

> We're getting close (one or two days out...) to pushing a new version 
> of the 1.1 spec, some 1.1 headers, and a beta 1.1 Windows 
> implementation out the door, and Dan brought something up with regard 
> to the headers...
> In the current universal 1.0 headers, there are still some #ifdef 
> LINUX sections in there which encompass functions which I think are 
> all deprecated:
> alHint
There is no code behind this guy. Could that be done the same way for 
the win32/macos implementations?  I see no need for it in 1.1 but an 
extension might want to use alHint as a mechanism to set acoustic effect 
qualities for example.  A dummy function could leave it open for future 
use and be cross-platform still.
> alGetListeneriv
> alGetSourceiv
The functionality is already covered by 'fv versions correct?

> alGetBufferiv
> alGetBufferfv
Same thing as alGetBuffer{i,v}, redundant.

> alQueuei
> various IASIG functions
>
> All these sections are Linux-branch specific.  Our inclination over 
> here -- if everyone can live with it -- is to finally dump (for 1.1) 
> all the above Linux-specific stuff so that we finally end up with 
> headers which are entirely cross-platform.  We'll proceed along those 
> lines if nobody objects...
I don't see a problem dropping them, cleaning up the header outweighs 
having to patch some existing code. I'm not aware of any commercial apps 
that used a dynamic library with the mentioned symbols anyways.  I think 
adding alHint as an empty function for win32/macos would be harmless though.
> Garin
>
> _______________________________________________
> openal-devel mailing list
> openal-devel@xxxxxxxxxxxxxxxxxxxxxxx
> http://opensource.creative.com/mailman/listinfo/openal-devel

--
James Tomaschke
Snr. Software Engineer
InfoSemiconductor, Inc.