Well, if adding redundant features cannot be avoided, would it be
possible for the opcode names not to begin with 'i' ?

Also, rather than adding new opcodes and a new set of API functions
for any future types, it may be preferred to extend the
invalue/outvalue opcodes to be able to handle multiple types, and
add a type argument to the callbacks.

It is a pity though that my work on the software bus is wasted.

On Friday 26 May 2006 21:24, Matt Ingalls wrote:

> i need instring/outstring opcodes comparable to invalue/outvalue
> 
> Unless i am missing something, it looks like it is going to be too much
> of a pain to use the software bus, as my frontend is designed around
> csound sending the fronend invalue/outvalue via callbacks whereas
> if i use the software bus my frontend has to call csound.
> 
> Any strong objection to me adding instring/outstring
> opcodes and their partner functions in the API?


_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net