Csound Csound-dev Csound-tekno Search About

[Cs-dev] UDO loading and optional parameters

Date2009-09-20 22:41
Fromjoachim heintz
Subject[Cs-dev] UDO loading and optional parameters
I'd like to suggest some improvements to the UDO facility, and ask  
whether this could be done (hopefully simple).

1. When I am loading a set of UDOs, I often have dependencies from one  
to another or several others. For instance, UDO A uses UDO B in its  
definition, and UDO C uses UDO D and E. In this case, I have to list  
the definitions in the orchestra header or an #include file in this  
way: B, A, D, E, C. If the definition of UDO A comes before the  
definition of UDO B, I get an error.
Can this be made more flexible? I wished to be able to write the  
definitions in arbitrary order.

2. Could there be optional parameters in the UDOs as there are in the  
usual opcodes? Then I could call an UDO with just the first argument  
of four, and the other values would come from their defaults. At the  
moment there is an error message whenever there is one argument missing.

3. Is it necessary that the UDO definitions must appear exactly at the  
end of the orchestra header or could this also be made more flexible?

Thanks -

	joachim

------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
Date2009-09-20 23:48
FromVictor Lazzarini
SubjectRe: [Cs-dev] UDO loading and optional parameters
Regarding 2.  you can use o and p for
default arguments (see for instance
http://www.csounds.com/udo/displayOpcode.php?opcode_id=53)

Victor


On 20 Sep 2009, at 22:41, joachim heintz wrote:

> I'd like to suggest some improvements to the UDO facility, and ask
> whether this could be done (hopefully simple).
>
> 1. When I am loading a set of UDOs, I often have dependencies from one
> to another or several others. For instance, UDO A uses UDO B in its
> definition, and UDO C uses UDO D and E. In this case, I have to list
> the definitions in the orchestra header or an #include file in this
> way: B, A, D, E, C. If the definition of UDO A comes before the
> definition of UDO B, I get an error.
> Can this be made more flexible? I wished to be able to write the
> definitions in arbitrary order.
>
> 2. Could there be optional parameters in the UDOs as there are in the
> usual opcodes? Then I could call an UDO with just the first argument
> of four, and the other values would come from their defaults. At the
> moment there is an error message whenever there is one argument  
> missing.
>
> 3. Is it necessary that the UDO definitions must appear exactly at the
> end of the orchestra header or could this also be made more flexible?
>
> Thanks -
>
> 	joachim
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9-12, 2009. Register  
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
Date2009-09-21 12:56
Fromjoachim heintz
SubjectRe: [Cs-dev] UDO loading and optional parameters
Great - thanks. It's clearly described at the manual page, actually ...

	joachim


Am 21.09.2009 um 00:48 schrieb Victor Lazzarini:

> Regarding 2.  you can use o and p for
> default arguments (see for instance
> http://www.csounds.com/udo/displayOpcode.php?opcode_id=53)
>
> Victor
>
>
> On 20 Sep 2009, at 22:41, joachim heintz wrote:
>
>> I'd like to suggest some improvements to the UDO facility, and ask
>> whether this could be done (hopefully simple).
>>
>> 1. When I am loading a set of UDOs, I often have dependencies from  
>> one
>> to another or several others. For instance, UDO A uses UDO B in its
>> definition, and UDO C uses UDO D and E. In this case, I have to list
>> the definitions in the orchestra header or an #include file in this
>> way: B, A, D, E, C. If the definition of UDO A comes before the
>> definition of UDO B, I get an error.
>> Can this be made more flexible? I wished to be able to write the
>> definitions in arbitrary order.
>>
>> 2. Could there be optional parameters in the UDOs as there are in the
>> usual opcodes? Then I could call an UDO with just the first argument
>> of four, and the other values would come from their defaults. At the
>> moment there is an error message whenever there is one argument
>> missing.
>>
>> 3. Is it necessary that the UDO definitions must appear exactly at  
>> the
>> end of the orchestra header or could this also be made more flexible?
>>
>> Thanks -
>>
>> 	joachim
>>
>> ------------------------------------------------------------------------------
>> Come build with us! The BlackBerry® Developer Conference in SF,  
>> CA
>> is the only developer event you need to attend this year. Jumpstart
>> your
>> developing skills, take BlackBerry mobile applications to market and
>> stay
>> ahead of the curve. Join us from November 9-12, 2009. Register
>> now!
>> http://p.sf.net/sfu/devconf
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart  
> your
> developing skills, take BlackBerry mobile applications to market and  
> stay
> ahead of the curve. Join us from November 9-12, 2009. Register  
> now!
> http://p.sf.net/sfu/devconf
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>


------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net