[question] retrieving version info *before* context ?

[waltje]

Hi all!

One cannot retrieve the library's version info (using "alGetString(AL_VERSION)") until after we have a context.

Is this a bug or a feature?

I would think retrieving that kind of info should "always work", regardless of context/device state?

(tested on 1.23.1-current, but also going back several releases)

[kcat]

On systems that can have multiple OpenAL drivers, the context dictates which driver the alGetString call will use. Without a context, it doesn't know whether it's querying OpenAL Soft, Rapture3D, Generic Software, etc. For other systems or where multiple drivers aren't used, the context is still needed for proper behavior, to help ensure the code won't fail or misbehave if used on such a system.

A new set of functions would be needed to be able to query drivers without first setting up a device and context.

[waltje]

OK, but what if a programmer simply wants to know the version of the actual library they'relinked to?  Not the drivers or extensions... the actual library.  Ifn't that what this function callwould be for, as in pretty much any other library out there? If I want to know what driver I am using, I would probably want to call a function that takesa 'device' as a parameter, etc? Just curious. Fred On Saturday, November 18, 2023 at 05:35:06 AM EST, kcat ***@***.***> wrote: On systems that can have multiple OpenAL drivers, the context dictates which driver the alGetString call will use. Without a context, it doesn't know whether it's querying OpenAL Soft, Rapture3D, Generic Software, etc. For other systems or where multiple drivers aren't used, the context is still needed for proper behavior, to help ensure the code won't fail or misbehave if used on such a system. A new set of functions would be needed to be able to query drivers without first setting up a device and context. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>