| I'd recommend a general section in the earlier part of the manual,
probably a subsection of "Syntax of the Orchestra". Perhaps could
call it "Signal Arrays (t-vars)" and place it after the section
"User-Defined Opcodes (UDO)"?
steven
On Tue, Oct 11, 2011 at 11:45 AM, wrote:
> I have added stuff about t-vars to the manual, but I do not knpw where to
> describe the t1[k1-2] style syntax. In many vars it belongs to
> expressions, but I have not found a suitable place
>
> Any suggestions?
>
> ==John ff
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2d-oct
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |