[linux-audio-dev] The global API namespace

David Olofson david at olofson.net
Sat Dec 7 00:00:28 UTC 2002


Just wondering how the h*ll you're supposed to name functions and 
types when all sensible naming conventions seem to be reserved by 
POSIX and other authorities...

How about this for Audiality:

	Functions:	a_whatever()
	Types:		at_whatever

I bet *some* lib is using a_* and/or at_*, but I have yet to find it. 
Besides, it doesn't look like a great idea to use both a_* and at_* 
for a single project - but *_t is reserved, and I don't like 
Capitalization in public APIs. Maybe I can make an exception, 
though... A_* and AT_* or something?

Then again, most compilers can tell types from functions without 
throwing too much bogus messages at the user, so one might get away 
with a single prefix and simply remove the _t everywhere.


//David Olofson - Programmer, Composer, Open Source Advocate

.- The Return of Audiality! --------------------------------.
| Free/Open Source Audio Engine for use in Games or Studio. |
| RT and off-line synth. Scripting. Sample accurate timing. |
`---------------------------> http://olofson.net/audiality -'
.- M A I A -------------------------------------------------.
|    The Multimedia Application Integration Architecture    |
`----------------------------> http://www.linuxdj.com/maia -'
   --- http://olofson.net --- http://www.reologica.se ---



More information about the Linux-audio-dev mailing list