File: foot.html

package info (click to toggle)
nyquist 3.12%2Bds-3
  • links: PTS, VCS
  • area: main
  • in suites: buster
  • size: 58,036 kB
  • sloc: ansic: 74,355; lisp: 20,485; java: 9,390; cpp: 6,695; sh: 207; xml: 58; makefile: 39
file content (46 lines) | stat: -rw-r--r-- 2,381 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
<body bgcolor="ffffff">
<h2>Footnotes</h2>
<a name = "foot1"> 1. </a>In the Common Music implementation of SAL, <code>=</code> compiles to the Lisp <code>=</code> function, so this is an incompatible difference.
<P>
<a name = "foot2"> 2. </a>In the Common Music implementation of SAL, <code>~=</code> compiles to the Lisp <code>equal</code> function, so this is an incompatible difference.
<P>
<a name = "foot3"> 3. </a>Most behaviors will stop at time 1, warped according to <code>*warp*</code> to some real time, but this is by convention and is not a direct specification.
<P>
<a name = "foot4"> 4. </a>Since XLISP does not support multiple value
returns, multiple value returns are simulated by having the function
assign additional return values in a list to the global
variable <code>*rslt*</code>. Since this is a global, it should be inspected
or copied immediately after the function return to insure that return
values are not overwritten by another function.
<P>
<a name = "foot5"> 5. </a>To be consistent, a blank line ought to specify zero attributes and 
generate a note that inherits all of its attributes from the previous one.
Adagio is intentionally inconsistent in this respect.
<P>
<a name = "foot6"> 6. </a>My TX816 Owner's Manual gives an incorrect format for the
change parameter sysex command (according to the manual, there is no data 
in the message!)  I am assuming that the data should be the last byte before
the EOX and that there is no byte count.  If you are reading this, assume
that I have not tested this guess, nor have I tested this example.
<P>
<a name = "foot7"> 7. </a>This is not part of standard XLISP nor is it built-in. Nyquist defines it though.
<P>
<a name = "foot8"> 8. </a>This is not a standard XLISP 2.0 function.
<P>
<a name = "foot9"> 9. </a>This is not a standard XLISP 2.0 function.
<P>
<a name = "foot10"> 10. </a>This is not a standard XLISP 2.0 function.
<P>
<a name = "foot11"> 11. </a>This is not a standard XLISP 2.0 function.
<P>
<a name = "foot12"> 12. </a>This is not a standard XLISP 2.0 function.
<P>
<a name = "foot13"> 13. </a>This is not a standard XLISP 2.0 function.
<P>
<a name = "foot14"> 14. </a>This is not a standard XLISP 2.0 function.
<P>
<a name = "foot15"> 15. </a>This is not a standard XLISP 2.0 function.
<P>
<a name = "foot16"> 16. </a>This is not a standard XLISP 2.0 function.
<P>
</body></html>