I was doing some maintenance on the manual and noted that the following
opcodes are not documented (or at least not obviously)

signalflowgraph
many functions involving arrays in arrayops.cpp
faustcompile2
faustdsp
faustplay
Many opcodes starting la_
OSCsend_lo
lincos
bpfcos
reshapearray
ftslice
tab2array
printarray

There may be others as I was not looking for undocumented ops, but these
just were noticed

The signal flow graph opcodes are documented, see
https://csound.com/docs/manual/SignalFlowGraphOpcodes.html.

Best,
Mike

-----------------------------------------------------
Michael Gogins
Irreducible Productions
http://michaelgogins.tumblr.com
Michael dot Gogins at gmail dot com
On Fri, Sep 21, 2018 at 2:51 PM John  wrote:
>
> I was doing some maintenance on the manual and noted that the following
> opcodes are not documented (or at least not obviously)
>
> signalflowgraph
> many functions involving arrays in arrayops.cpp
> faustcompile2
> faustdsp
> faustplay
> Many opcodes starting la_
> OSCsend_lo
> lincos
> bpfcos
> reshapearray
> ftslice
> tab2array
> printarray
>
> There may be others as I was not looking for undocumented ops, but these
> just were noticed
>

I agree tat outlet, inet,...etc are documented but  did not find in the 
sources any manual page for the opcode signalflowgraph, nor any use in 
examples.

The faust ops are new and I
forgot to document then. Will do.

I'm not sure about the others.

Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy
Maynooth University
Ireland

> On 21 Sep 2018, at 19:52, John  wrote:
> 
> I was doing some maintenance on the manual and noted that the following
> opcodes are not documented (or at least not obviously)
> 
> signalflowgraph
> many functions involving arrays in arrayops.cpp
> faustcompile2
> faustdsp
> faustplay
> Many opcodes starting la_
> OSCsend_lo
> lincos
> bpfcos
> reshapearray
> ftslice
> tab2array
> printarray
> 
> There may be others as I was not looking for undocumented ops, but these
> just were noticed
> 

As there is no manual page for the opcode signalflowgraph should it not be 
removed?  I think all opcodes should be documented.

On Fri, 21 Sep 2018, jpff wrote:

> I agree tat outlet, inet,...etc are documented but  did not find in the 
> sources any manual page for the opcode signalflowgraph, nor any use in 
> examples.
>
> John ff

csound -z says otherwise

sfpreset            shaker              shiftin             shiftout
signalflowgraph     signum              simple              sin
sinh                sininv              sinsyn              sleighbells


========================
Prof. Victor Lazzarini
Dean of Arts, Celtic Studies, and Philosophy,
Maynooth University,
Maynooth, Co Kildare, Ireland
Tel: 00 353 7086936
Fax: 00 353 1 7086952 

> On 27 Sep 2018, at 13:18, Michael Gogins  wrote:
> 
> There is no "signalflowgraph opcode", there is a SET of opcodes. 
> 
> All of the code for all of these opcodes is in the one Opcoces/signalflowgraph.cpp file. Perhaps this is the source of your confusion?
> 
> ALL OF THESE OPCODES ARE INDEED DOCUMENTED.
> 
> DO NOT REMOVE THIS FILE, the opcodes not only are documented in the official Csound Reference Manual, they are used by me and by other composers.
> 
> I have NO idea what you are talking about.
> 
> Best,
> Mike
> 
> 
> On Thu, Sep 27, 2018, 07:48 jpff  wrote:
> As there is no manual page for the opcode signalflowgraph should it not be 
> removed?  I think all opcodes should be documented.
> 
> On Fri, 21 Sep 2018, jpff wrote:
> 
> > I agree tat outlet, inet,...etc are documented but  did not find in the 
> > sources any manual page for the opcode signalflowgraph, nor any use in 
> > examples.
> >
> > John ff

Sorry but there is an opcode named signalflowgraph.  It appears in -z output and is defined in the file Opcodes/signalflowgraph.cpp as the first opcode in the OEntries.

I am not talking about the the collection, just that one opcode.  Not at a real computer yet so cannot give the line number etc

⁣Sent from TypeApp ​

On Sep 27, 2018, 13:19, at 13:19, Michael Gogins  wrote:
>There is no "signalflowgraph opcode", there is a SET of opcodes.
>
>All of the code for all of these opcodes is in the one
>Opcoces/signalflowgraph.cpp file. Perhaps this is the source of your
>confusion?
>
>ALL OF THESE OPCODES ARE INDEED DOCUMENTED.
>
>DO NOT REMOVE THIS FILE, the opcodes not only are documented in the
>official Csound Reference Manual, they are used by me and by other
>composers.
>
>I have NO idea what you are talking about.
>
>Best,
>Mike
>
>
>On Thu, Sep 27, 2018, 07:48 jpff  wrote:
>
>> As there is no manual page for the opcode signalflowgraph should it
>not be
>> removed?  I think all opcodes should be documented.
>>
>> On Fri, 21 Sep 2018, jpff wrote:
>>
>> > I agree tat outlet, inet,...etc are documented but  did not find in
>the
>> > sources any manual page for the opcode signalflowgraph, nor any use
>in
>> > examples.
>> >
>> > John ff
>> >