Well, all functions that refer to the state of an individual Csound
instance, and not ALL Csound instances, should take a Csound * first
parameter. In this case, the function is appending data to a static table
that is shared by ALL Csound instances - or at least that's what I intended.

============================================
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: Saturday, November 29, 2003 2:04 AM
Subject: [CSOUND-DEV:3577] host API: csoundAppendOpcode


> Hi all,
>
> I'm in the middle of getting csound.c to work with csound5 (using an
> extracted csoundCore.h from cs.h) and got stuck trying to edit
> csoundAppendOpcode.  It doesn't seem to have been designed to take in a
> csound *.  May I ask what the design decision is for this, and would it
> break anything if I changed it so that *ALL* host API functions
> currently in csound.h/csound.c take in a csound*?
>
> Thanks,
> steven
>


--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .

Okay, what you intended makes sense, but:

  OENTRY        *opcodlst_;
  void          *opcode_list_;   /* IV - Oct 31 2002 */
  OENTRY        *oplstend_;

is currently pushed into ENVIRON.  That makes sense to me too to have
separate opcodlst's per ENVIRON, same as running multiple scripts and
each instance of the scripting engine having it's own list of functions
imported, etc.

If this is okay, then the following function may need to be reworked
within the host API:

csoundNewOpcodeList
csoundDisposeOpcodeList
csoundAppendOpcode
csoundOpcodeCompare
csoundOpcodeDeinitialize

As some of these function don't work in the current context of how
ENVIRON is designed.

steven



On Sat, 2003-11-29 at 05:37, gogins@pipeline.com wrote:
> Well, all functions that refer to the state of an individual Csound
> instance, and not ALL Csound instances, should take a Csound * first
> parameter. In this case, the function is appending data to a static table
> that is shared by ALL Csound instances - or at least that's what I intended.
> 
> ============================================
> 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/
> ============================================