Hey
Using the CsoundOpcodeList i can get the name of all opcodes, the type of
their In-and out types. How can i get the _name_ of the In-and out types? I
don´t see a function for that in the API.

Thanks
Carsten
-- 
View this message in context: http://www.nabble.com/how-to-get-name-of-in--and-outtypes-tp15883754p15883754.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https:/

It would be really nice with a standardized "database" of the opcodes
with their syntax (in/out types and names). It could be an easy parsable
textfile distributed with csound, and the API might even include either
a function to get the location of this file or even functions to parse
it. Or, perhaps even better: the textfile could be written in C syntax
as an includable .h header file.

Steven Yi wrote:
> Hi Carsten,
> 
> There are no names for the in/out types.  That meta-information is
> only really available in the manual.  However, it is not too difficult
> to parse the manual to find the information, and it may be better to
> do that as using CsoundOpcodeList may report opcodes which are really
> only meant to be used internally to csound.
> 
> steven
> 
> On Thu, Mar 6, 2008 at 12:53 PM, Carsten Hoyer  wrote:
>>  Hey
>>  Using the CsoundOpcodeList i can get the name of all opcodes, the type of
>>  their In-and out types. How can i get the _name_ of the In-and out types? I
>>  don´t see a function for that in the API.
>>
>>  Thanks
>>  Carsten
>>  --

-- 
/Jonatan         [ http://kymatica.com ]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

i've always wanted something added either to the API
or the opcodelist struct for this.   opcodes would either register a  
callback
to return the syntax or it would just be included directly in the  
OENTRY.

   the benefit of this over a file is that it would always be up-to- 
date and always
work no matter what opcodes were installed.

the trick would be how to handle opcodes with multiple rates and  
hidden ones
like steven mentioned (although for those i guess they could just not  
register
the info )

-m

On Mar 6, 2008, at 4:07 PM, Jonatan Liljedahl wrote:

> It would be really nice with a standardized "database" of the opcodes
> with their syntax (in/out types and names). It could be an easy  
> parsable
> textfile distributed with csound, and the API might even include  
> either
> a function to get the location of this file or even functions to parse
> it. Or, perhaps even better: the textfile could be written in C syntax
> as an includable .h header file.
>
> Steven Yi wrote:
>> Hi Carsten,
>>
>> There are no names for the in/out types.  That meta-information is
>> only really available in the manual.  However, it is not too  
>> difficult
>> to parse the manual to find the information, and it may be better to
>> do that as using CsoundOpcodeList may report opcodes which are really
>> only meant to be used internally to csound.
>>
>> steven
>>
>> On Thu, Mar 6, 2008 at 12:53 PM, Carsten Hoyer  
>>  wrote:
>>> Hey
>>> Using the CsoundOpcodeList i can get the name of all opcodes, the  
>>> type of
>>> their In-and out types. How can i get the _name_ of the In-and out  
>>> types? I
>>> don´t see a function for that in the API.
>>>
>>> Thanks
>>> Carsten
>>> --
>
> -- 
> /Jonatan         [ http://kymatica.com ]
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

matt ingalls
development@gvox.com




-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks both
I actually made the code to get the information from the manual ½ a year
ago. But I was convinced that it would be better to intergrate it directly
from source, for some of the same reasons as Matt points out. Guess not :)

Carsten


-- 
View this message in context: http://www.nabble.com/how-to-get-name-of-in--and-outtypes-tp15883754p15891118.html
Sent from the Csound - Dev mailing list archive at Nabble.com.


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/