jpff@maths.bath.ac.uk wrote:

> BTW, in your icall there is an error related to the carry flag, as it
> is static/local to the file in your code, but it needs to be global.
> ==John ffitch

Could you be more explicit about the carry error? The icall opcode seems to operate OK
with my compiler. Where is the bug?

kargc, argc, krtrnc & company, are very useful to handle a and k-rate function parameter
passing. 
Using these opcodes together with icall, it is possible to convert Csound in a sort of
structured language, with user-defined procedures and functions which accept and return
more than one parameter a time. I developed a four-voice time-variant real-time polyphonic
pitch-shifter using these opcodes, but it can be very easily expanded to handle more
voices with very low programming efforts, because the code of each voice (as well as the
code of each pitch generator) is simply a subroutine accepting parameters from the
outside.

I think that icall, schedule etc. opcodes, when used together, are a very important
feature of Csound language for the reasons showed above.

-- 
Gabriel Maldonado

http://www.agora.stm.it/G.Maldonado/home2.htm