I have just committed changes to rename all of the public Cscore functions,
export them, etc.  Access to the Cscore API is by #including "cscore.h".

(I've made the functions "PUBLIC" for Windows exporting and I've taken care
of exporting on MacOS 9.  Is there anything else that I need to do to make
sure that all of the new API functions I'm adding also get exported on linux
and MacOS X?)

I've also changed the formerly internal function cscorinit() into the now
public API function csoundInitializeCscore(), available from csound.h.  This
function prepares a csound instance for "standalone" Cscore processing --
that is, using Cscore without compiling an orchestra or performing the
score.

To show how to use this new functionality, I have converted the cscormai.c
stub for making standalone Cscore programs into a client of the API.  There
is still some work to be done in this -- not everything works yet.  In
particular, the lplay() function -- now cscoreListPlay() -- won't work in
standalone mode.  I have to rethink the purpose of this function (and
possibly eliminate it).

There are still problems with Cscore causing memory exceptions on my system.
And I guess that all of the statics in cscorfns.c never were removed, so
that still needs to be done.  But, everything should compile for the time
being.

Anthony Kozar
anthonykozar AT sbcglobal DOT net
http://akozar.spymac.net/



-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net