[Openal-devel] alcSuspendContext()

[Garin Hiebert]

> Reading the annotations, it certainly seems this was the case.

It's a relic from the Loki days, then, and was one of the under-defined 
sections of the 1.0 spec.  I doubt if anyone outside of Loki ever used 
suspend and process for anything other than batching state-changes 
together.  Going forward, it would seem practical to just follow current 
practice.

I'm pretty sure that the 1.1 documentation -- both the spec and 
Programmer's Guide -- states things the Creative way (while not fanning 
any flames by bringing up alternatives or referencing an argument).

Optional Side note for those who haven't been rabidly following OpenAL 
the last eight years -- The OpenAL 1.0 spec was developed while the 
implementations were being used for publishing games.  This helped make 
OpenAL a very pragmatic API, but also resulted in confusion around 
issues such as this where the spec never really caught up with what was 
being implemented, or where there were multiple competing ways of 
interpreting the API.  That was mostly cleaned up with OpenAL 1.1, and 
the emergence of OpenAL-soft should help in nailing down remaining cases.

Garin