Hi,
I was generating automatically UDO from html reference.
Now, is there anywhere a (structured) list (a text file is enough) of 
opcode so that I can parse it?

Reference folder is wiki-style: all together.
As an example, I'd like to generate all the available Ugens.
So I need to have: 1. signal generators, 2. maths, 3.etc.

Thanks

-a-

Andrea Valle
DAMS - Facoltà di Scienze della Formazione
Università degli Studi di Torino
http://www.semiotiche.it/andrea
andrea.valle@unito.it

I think you can retrieve a list using a csound API function. I had to 
get a list like this or Lettuce so I quickly wrote a little application 
that parsed the help file for opcodes and parameters. If one of the 
developers knows of the API function that can retrieve all opcodes I can 
try it. Otherwise I think you can look through entry1.h in the csound 
src, afaik that lists all opcodes. Of course you will have to classify 
them into their particular groups yourself.

Rory.



andrea valle wrote:
> Hi,
> I was generating automatically UDO from html reference.
> Now, is there anywhere a (structured) list (a text file is enough) of 
> opcode so that I can parse it?
> 
> Reference folder is wiki-style: all together.
> As an example, I'd like to generate all the available Ugens.
> So I need to have: 1. signal generators, 2. maths, 3.etc.
> 
> Thanks
> 
> -a-
> 
> Andrea Valle
> DAMS - Facoltà di Scienze della Formazione
> Università degli Studi di Torino
> http://www.semiotiche.it/andrea
> andrea.valle@unito.it

Thanks,
yes, the problem is that I do not want to classify by hand.
Something like this would be nice:

http://www.sfu.ca/sca/Manuals/Csound/2/p.html

(but it's a bit out of date...)

-a-


On 16 May 2006, at 14:49, Rory Walsh wrote:

> I think you can retrieve a list using a csound API function. I had to 
> get a list like this or Lettuce so I quickly wrote a little 
> application that parsed the help file for opcodes and parameters. If 
> one of the developers knows of the API function that can retrieve all 
> opcodes I can try it. Otherwise I think you can look through entry1.h 
> in the csound src, afaik that lists all opcodes. Of course you will 
> have to classify them into their particular groups yourself.
>
> Rory.
>
>
>
> andrea valle wrote:
>> Hi,
>> I was generating automatically UDO from html reference.
>> Now, is there anywhere a (structured) list (a text file is enough) of 
>> opcode so that I can parse it?
>> Reference folder is wiki-style: all together.
>> As an example, I'd like to generate all the available Ugens.
>> So I need to have: 1. signal generators, 2. maths, 3.etc.
>> Thanks
>> -a-
>> Andrea Valle
>> DAMS - Facoltà di Scienze della Formazione
>> Università degli Studi di Torino
>> http://www.semiotiche.it/andrea
>> andrea.valle@unito.it
> -- 
> Send bugs reports to this list.
> To unsubscribe, send email to csound-unsubscribe@lists.bath.ac.uk
>
>
Andrea Valle
DAMS - Facoltà di Scienze della Formazione
Università degli Studi di Torino
http://www.semiotiche.it/andrea
andrea.valle@unito.it