There are quite a few functions beginning with "csound" that are not public
API functions.  They are more like "internal APIs" -- functions that someone
expected would be called by other parts of the Csound engine.  Some of them
may also have been candidates at one time for inclusion in the public API.
(And a few were public but then privatized for various reasons).

I think Istvan named a lot of functions this way and he tried to make sure
most other functions were declared static.  I have imitated this practice
myself.

I don't think that there are currently any symbols not marked PUBLIC in the
code that should be.  I agree that libraries should be built so that only
the PUBLIC functions are exported.  I have had warnings while building
Cscore programs on OS X because the framework library is improperly
exporting private symbols.

Anthony

Felipe Sateler wrote on 9/14/07 12:17 AM:

> What is interesting is that several functions are not PUBLIC, but have
> documentation, and have suggesting names, which makes me think they should be
> (I don't really know the csound API). Examples include:
> 
> csoundGetMidiChannel
> csoundGetMidiChannelNumber
> csoundGetOpcodeName
> csoundGetPFields
> csoundLoadModules
> csoundLoadSoundFile
> 
> among many others (there seem to be around 939 symbols that were exported but
> now aren't).


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net