In general, I think if somebody has contributed something to Csound that is 
used a certain way, has a certain signature, later developers must respect 
that and preserve the usage for backward compatibility.

I do not think there is any problem with defining a NEW opcode with the 
signature that YOU like, even if it uses the same code, or you could do the 
same thing with a user-defined opcode... as long as you leave the existing 
usage intact.

One of the great strengths of Csound is the expectation that old code, 
instrument definitions, etc. will continue to run out of the box. This 
increases the power of Csound much more than adding oodles of new opcodes 
etc. because the body of usable code keeps growing and does not lose older 
stuff.


----- Original Message ----- 
From: "Andres Cabrera" 
To: "Csound-dev" 
Sent: Sunday, February 13, 2005 12:35 PM
Subject: [Cs-dev] vtable


> Hi all, especially Gab,
>
> I'm starting to write the documentation for the CsoundAV opcodes ported to 
> csound5, (thanks Steven and Michael for the great work with the manual 
> repository), and I'm wondering if the syntax for vtablei and similar 
> should be changed.
> Currently the syntax is:
>
> vtablei  indx, ifn, interp, ixmode, iout1 [, iout2, iout3, .... , ioutN ]
> vtablek  kndx, kfn, kinterp, ixmode, kout1 [, kout2, kout3, .... , koutN ]
> vtablea  andx, kfn, kinterp, ixmode, aout1 [, aout2, aout3, .... , aoutN ]
>
> vtabi  indx, ifn, iout1 [, iout2, iout3, .... , ioutN ]
> vtabk  kndx, ifn, kout1 [, kout2, kout3, .... , koutN ]
> vtaba   andx, ifn, aout1 [, aout2, aout3, .... , aoutN ]
>
>
> but maybe it should be:
> iout1 [, iout2, iout3, .... , ioutN ] vtablei indx, ifn, interp, ixmode
>
> Is there a reason for this unusual opcode behaviour (outputs on the 
> right)?
>
> Cheers,
> Andrés
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

You're right. No sense fixing what's not broken. It was just an idea 
since these opcodes are new in csound5.

Andrés

Michael Gogins wrote:
> In general, I think if somebody has contributed something to Csound that 
> is used a certain way, has a certain signature, later developers must 
> respect that and preserve the usage for backward compatibility.
> 
> I do not think there is any problem with defining a NEW opcode with the 
> signature that YOU like, even if it uses the same code, or you could do 
> the same thing with a user-defined opcode... as long as you leave the 
> existing usage intact.
> 
> One of the great strengths of Csound is the expectation that old code, 
> instrument definitions, etc. will continue to run out of the box. This 
> increases the power of Csound much more than adding oodles of new 
> opcodes etc. because the body of usable code keeps growing and does not 
> lose older stuff.
> 
> 
> ----- Original Message ----- From: "Andres Cabrera" 
> To: "Csound-dev" 
> Sent: Sunday, February 13, 2005 12:35 PM
> Subject: [Cs-dev] vtable
> 
> 
>> Hi all, especially Gab,
>>
>> I'm starting to write the documentation for the CsoundAV opcodes 
>> ported to csound5, (thanks Steven and Michael for the great work with 
>> the manual repository), and I'm wondering if the syntax for vtablei 
>> and similar should be changed.
>> Currently the syntax is:
>>
>> vtablei  indx, ifn, interp, ixmode, iout1 [, iout2, iout3, .... , ioutN ]
>> vtablek  kndx, kfn, kinterp, ixmode, kout1 [, kout2, kout3, .... , 
>> koutN ]
>> vtablea  andx, kfn, kinterp, ixmode, aout1 [, aout2, aout3, .... , 
>> aoutN ]
>>
>> vtabi  indx, ifn, iout1 [, iout2, iout3, .... , ioutN ]
>> vtabk  kndx, ifn, kout1 [, kout2, kout3, .... , koutN ]
>> vtaba   andx, ifn, aout1 [, aout2, aout3, .... , aoutN ]
>>
>>
>> but maybe it should be:
>> iout1 [, iout2, iout3, .... , ioutN ] vtablei indx, ifn, interp, ixmode
>>
>> Is there a reason for this unusual opcode behaviour (outputs on the 
>> right)?
>>
>> Cheers,
>> Andrés
>>
>>
>> -------------------------------------------------------
>> SF email is sponsored by - The IT Product Guide
>> Read honest & candid reviews on hundreds of IT Products from real users.
>> Discover which products truly live up to the hype. Start reading now.
>> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
> 
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 
> 
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net