Csound Csound-dev Csound-tekno Search About

[CSOUND-DEV:4795] Re: --list-opcodes seems busted

Date2004-06-02 01:50
From"Michael Gogins"
Subject[CSOUND-DEV:4795] Re: --list-opcodes seems busted
Please do!

The -z1 option does print the inputs and outputs from the OENTRY records,
but as you said, you can't get --list-opcodes to do it. --list-opcodes
_does_ do what -z does, though.

----- Original Message ----- 
From: "steven yi" 
To: "Csound Developers Discussion List" 
Sent: Tuesday, June 01, 2004 7:30 PM
Subject: [CSOUND-DEV:4792] --list-opcodes seems busted


> Hi all,
>
> Just to make sure, using --list-opcodesN (where N is a number) is
> supposed to output the opcodes in a list showing their inputs and
> outputs as listed in their OENTRY, yes?  Either way, using this form of
> the --list-opcodes doesn't seem to do anything.
>
> Another question, would anyone mind if I added a little message to the
> default usage output to mention that --help shows long help and that
> there are more flags than are available only with short options.  I
> think many users might not even realize or easily forget that the other
> options are there.
>
> Thanks,
> steven
>

Date2004-06-02 06:09
Fromstevenyi
Subject[CSOUND-DEV:4802] Re: --list-opcodes seems busted
Ah that's great!  I didn't know about the -z1 option.  I'm going to see
about fixing it up for --list-opcodes tonight, as well as add in the
extra note for the --help option.

Thanks!
steven

On Tue, 2004-06-01 at 17:50, Michael Gogins wrote:
> Please do!
> 
> The -z1 option does print the inputs and outputs from the OENTRY records,
> but as you said, you can't get --list-opcodes to do it. --list-opcodes
> _does_ do what -z does, though.
> 
> ----- Original Message ----- 
> From: "steven yi" 
> To: "Csound Developers Discussion List" 
> Sent: Tuesday, June 01, 2004 7:30 PM
> Subject: [CSOUND-DEV:4792] --list-opcodes seems busted
> 
> 
> > Hi all,
> >
> > Just to make sure, using --list-opcodesN (where N is a number) is
> > supposed to output the opcodes in a list showing their inputs and
> > outputs as listed in their OENTRY, yes?  Either way, using this form of
> > the --list-opcodes doesn't seem to do anything.
> >
> > Another question, would anyone mind if I added a little message to the
> > default usage output to mention that --help shows long help and that
> > there are more flags than are available only with short options.  I
> > think many users might not even realize or easily forget that the other
> > options are there.
> >
> > Thanks,
> > steven
> >
> 
>