[Openal-devel] Misc OpenAL SI questions/requests
Panne Sven Com MD PBM IPM TPS 4
sven.panne at siemens.com
Thu Aug 18 02:21:29 PDT 2005
Hmmm, I still haven't seen a very compelling reason for the split of the header files. The current split is very arbitrary and random, e.g. typedefs for a single type are sometimes in one part, sometimes in the other, depending on the platform. And we definitely need some preprocessor trickery in al.h, anyway (ALAPI/ALAPIENTRY), but this is quite harmless. And OpenGL doesn't do a similar split, either...
So are there any real objections against merging the parts? Let's keep things simple!
> -----Original Message-----
> From: openal-devel-admin at opensource.creative.com
> [mailto:openal-devel-admin at opensource.creative.com] On Behalf
> Of James Tomaschke
> Sent: Montag, 15. August 2005 19:33
> To: openal-devel at opensource.creative.com
> Subject: Re: [Openal-devel] Misc OpenAL SI questions/requests
> Andrew McDonald wrote:
> I see using altypes.h for a different reason. Instead of
> being a file that the platform provides, it is a bunch of
> #if/#else blocks for the various supported AL platforms. By
> keeping the two header files seperate you can get rid of all
> the platform #if/#else clutter in al.h.
> My current altypes.h has:
> #define AL_TRUE 1
> #define AL_SOURCE_TYPE 0x200
> I would rather see the latter in al.h, and leave altypes.h
> for just platform typedefs.
> That's just the way I would do it, not that the current
> method has any flaws.
More information about the Openal-devel