| I was thinking about this the other day. Having a text file that is
manually updated will of course always run the risk of being out-of-date. I
asked a long time ago for a feature within Csound that would print out the
opcodes in each library.
I am wondering how hard would this be to do? Not very hard would be my
guess. Should be as simple as saving a string with the name of each library
as it is loaded and then saving a pointer to that string for each opcode as
it is added.
I would then suggest adding a -z2 option for printing a list of opcodes in
order with their library locations, and possibly a -z3 option for printing a
list sorted by the library name.
If the other developers like this idea, I could look into implementing it.
Anthony
Art Hunkins wrote on 12/8/06 8:47 PM:
> I'd like to request that Loadable_Opcodes.txt be updated to show where all
> current opcodes are located (in which library).
>
> I have come to rely on this file substantially, as I routinely work with
> only the collection of .dll's I actually need. Recently, I've wanted to use
> the "changed" opcode, and there is no ready source of information on what
> library includes it. (I presume it is located in one of the recently added
> libraries, probably in the group Andres ported from CsoundAV.)
>
> Andres?
>
> Art Hunkins
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |