aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMarshall Lochbaum <mwlochbaum@gmail.com>2020-10-30 18:43:11 -0400
committerMarshall Lochbaum <mwlochbaum@gmail.com>2020-10-30 18:43:11 -0400
commite5b583cfec589988ce980aef7366308a6321ff8e (patch)
tree879465b1c2054e3fec4a49059bc38146de1050ce /docs
parentff1453f2e2d086a984905bbb85a89712ea3c78bb (diff)
Remove superceded code block showing evaluation order
Diffstat (limited to 'docs')
-rw-r--r--docs/tutorial/expression.html4
1 files changed, 0 insertions, 4 deletions
diff --git a/docs/tutorial/expression.html b/docs/tutorial/expression.html
index 22da2272..d1a1d32a 100644
--- a/docs/tutorial/expression.html
+++ b/docs/tutorial/expression.html
@@ -347,10 +347,6 @@
</table>
<p>It's past time we covered how the syntax for modifiers works. Remember how I told you you hated learning the order of operations? No? Good. Modifiers bind more tightly than functions, so they are called on their operands before their operands can be used. As the parentheses above suggest, modifiers also associate from left to right, the opposite order as functions. For example, the first expression above is evaluated in the order shown below. First we construct the square function <code><span class='Function'>×</span><span class='Modifier'>˜</span></code>, then compose it with <code><span class='Function'>+</span></code>, and finally apply the result to some arguments.</p>
-<pre> <span class='Function'>=</span> <span class='Function'>×</span><span class='Modifier'>˜</span>
- <span class='Modifier2'>∘</span><span class='Function'>+</span>
- <span class='Number'>3</span> <span class='Number'>4</span>
-</pre>
<svg viewBox='-213 -34 512 134'>
<g font-family='BQN,monospace' font-size='18px'>
<rect class='code' stroke-width='1' rx='10' x='-21.5' y='-24' width='129' height='114'/>