logo       

Newcomer questions: msg#00000

lib.openal.devel

Subject: Newcomer questions

Hello all, I've read the list archives up to March 2005 so far (and
also the last few months) and I'll try to finish reading the rest as
soon as possible. So here are some question I have, mostly about the
SI, since I'm on Linux:

Why is __func__ not used? I've seen a few spots where it'd be useful,
it's C99, supported on Linux, Solaris, Irix and I think XCode, and
MSVC supports __FUNCTION__ (also supported by gcc, which supports
both). Is it frowned upon or just has no one used it so far?

Is the function _alCheckRangeb needed at all? It's trivial enough to
be a macro (it's only called from al_source.c , so it wouldn't cause
bloat). And probably no comparisons against AL_TRUE should be made?
Comparisons against AL_FALSE would probably be better, since false ==
0 and true != 0 are their most 'simple' definitions. I don't think GL
makes any guarantees about their values, which could be a
compatibility problem?
In a related issue, AL_TRUE is defined as '8-bit boolean', while the
GL spec says that the minimum bit width of a boolean is 1.

mixaudio16.c includes 65 mixer functions plus a generic one, I
thought Prakash Punnoor had submitted a patch that simplified that?
Maybe the answer to this is in the archive and I just haven't reached
it yet :)

Is the format of openalrc documented anywhere? Recently we discussed
adding a way for a user to switch dynamically between different
speaker setups in Gnome or KDE using a simple applet, the headphone to
5.1 transition being an example. Any way to do this dynamically and
externally (i.e. not modifying an app)?

Cheers,
Matias D'Ambrosio


<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise