Hi Istvan,

> The problem with this is that by default outvalue just discards the
> data, while invalue always returns 0. These opcodes are only useful
> if the host application registers invalue/outvalue callbacks, but then
> the functionality depends on the actual implementation.
> However, if I understand correctly, you want something like i/k-rate
> ZAK space indexed by strings, defaulting to zero for undefined
> locations ?

Well, using invalue and outvalue was a bit hackish in the first place,
and now at least i know that it's really not usable for this!  I
didn't try any of the code out I wrote, just speculating.  I think
your description of a " i/k-rate ZAK space indexed by strings,
defaulting to zero for undefined locations" is exactly what I am
interested in, except no zakinit type of operation would be necessary.
 
> > Now, I think invalue doesn't work with S strings (need to check), and
> 
> All opcodes that expect a quoted string as input argument should work
> with S variables as well (in fact this is completely transparent), although
> some may not expect that the variable can change.
> What invalue/outvalue really does not support yet is strings as data
> rather than just index.

Well, using invalue/outvalue doesn't sound like a good idea for the
purpose I mentioned due to what you mentioned, and I seem to remember
Matt having something like string values in MacCsound now.  I had done
"csound -z1" and it's opcode signature showed "T" and not "S", and I
didn't think they were compatible. Are they?

> > Stable1 concat "myInstrument_tab1_", i_instr_id
> 
> This can be done at i-time with
> 
> Stable1 sprintf "myInstrument_tab1_%d", i_instr_id
> of course, an opcode for this specific purpose may be more efficient,
> but you can already use sprintf/sprintfk to have much of the functionality
> of the C version of sprintf.

Ah, that is much easier! :) 

steven
-- 
Send bugs reports to this list.
To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk