Thanks for the info. I am sure we can get this all working in csound 5.

============================================
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, December 29, 2003 10:29 AM
Subject: [CSOUND-DEV:3846] Re: csound5


> Hi Michael and all,
>
> > 4. Replace jpff_glue.c with an improved csound.c, which in turn requires
> > some redesign of the existing Csound API. At a minimum, the
QueryInterface
> > approach will be used to provide for enhanced future extensibility (new
> > APIs for bus, drivers, etc.).
>
> I had started on using csound.c and load_opcodes.c in place of
> jpff_glue.c and dl_opcodes.c in csound5.  However, in trying to keep
> both options usable, I ran up against a wall.  The problem was in
> main.c, as it defines csoundCompile, which is in csound.c, and also that
> it is now what csoundMain used to be in csound4.  So using csoundMain
> from the API functions doesn't quite work if using csound.c.
>
> These two diverging source codes are incompatible now, and the more they
> continue on separately the more difficult it's going to be for
> integration, IMO.  I would prefer to use the csound.c/load_opcodes.c
> code and perhaps integrating into it whatever is necessary from
> jpff_glue.c/dl_opcodes.c rather than the other way.
>
> FYI: I did spend time updating the code in csound.c in csound5 so it is
> a little different than csound4.
>
> steven
>