Re: how to access opcodes without the csound engine ?

> This is a good idea, and I have thought about it myself. It would take
> a fair amount of work, but it might be well worth while. There are
> several issues
>
> (1) The opcodes might have to be "wrapped" in some abstraction layer,
> like a C++ virtual class for opcodes that exposes all the opcode
> hooks. But the existing opcode table might actually be enough, as it
> already contains all the function pointers and in/out type codes. So,
> such an abstraction layer could be quite thin, a skinny C++ class that
> plugs the opcode structure and function pointers into a more
> accessible form, perhaps with template metaprogramming to
> automagically create getters/setters for all the in/out values.
>
> (2) Many opcodes call back into Csound, and often directly access
> objects in Csound. So, that part of the Csound "host:" would have to
> be re-implemented in a wrapper by the new host. Actually, I don't
> think doing this is necessarily so hard, especially since a lot of
> opcodes do this via the Csound API now, and the rest could be changed
> to use the API. Then all that is required is to re-implement those
> Csound API calls in the new host. A lot of this is easy - rates,
> messaging, etc. Function table access, not so hard. Memory management,
> a  bit harder. I don't know what else would be required.