Comment 6 for bug 273558

Hi Y'all,

Could someone please tell me what binary functionality has been changed/removed from libopenal with this change?

I understand that the implementation has been changed radically. But OpenAL is an API for general access to abstract sound hardware. So...what _can't_ I do with libopenal.so.1 that I _can_ do with libopenal.so.0?

- Are there any APIs whose names have changed, been removed, or whose arguments have shifted? If so, what?
- Did the method of translating an API to an ABI change with this DLL?
- Is it simply the case that there are OpenAL extensions that are now no longer present?

(In the last case, it would be wrong for apps to link to OpenAL extensions - they should clearly be accessed with dlsym or something like it.)

I ask for two reasons:
1. If an API or ABI really changed, then simply linking against libopenal.so.1 (or dlopening whatever is on the disk) will not be enough, because something is different.
2. We have users who are simply symlinking a fake libopenal.so.0 from libopenal.so.1 and they claim it works. We can update our current products, but not ones that are out of development, so we need to know if this work-around makes any sense.

If the conclusion of this bug is "ABI changed, apps must recompile", someone please post a link to whatever it is that changed!

/ben