| Not exactly... the header files need to be reorganized. Currently there is
not a good separation in the header files, and too many internal things need
to be exposed in the API.
As a first step, we should probably move as much of cs.h into csound.h as we
need (but no more) to ensure that plugin opcodes ONLY need csound.h for
anything they want to do.
============================================
Michael Gogins
gogins at pipeline period com
Irreducible Productions
CsoundVST, an extended version of Csound for programming music and sound
Available at http://sourceforge.net/projects/csound/
============================================
----- Original Message -----
From: "stevenyi"
To: "Csound Developers Discussion List"
Sent: Monday, November 17, 2003 12:39 AM
Subject: [CSOUND-DEV:3352] Re: Road to Reentrancy
> Hi all,
>
> It seems to me now that opcode plugins, since they won't be using the
> API functions as defined in csound.h but rather should be accessing
> through the GLOBAL *, then csound.h can be considered the host API and
> cs.h in it's current form is something that would eventually become a
> plugin API, yes?
>
> steven
> |