aboutsummaryrefslogtreecommitdiff
path: root/doc/block.md
diff options
context:
space:
mode:
authorMarshall Lochbaum <mwlochbaum@gmail.com>2021-07-18 17:53:37 -0400
committerMarshall Lochbaum <mwlochbaum@gmail.com>2021-07-18 17:53:37 -0400
commit7e0e38bd155fab76fa3b6776f9184611d044903d (patch)
tree9cbd13e8aae249cb97b1dd2b22a084817093890c /doc/block.md
parentbbecd676b7c127fead3ef172bbae3ddf2fb7f19a (diff)
Finish lexical scope documentation
Diffstat (limited to 'doc/block.md')
-rw-r--r--doc/block.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/block.md b/doc/block.md
index 75550a94..674d7d9f 100644
--- a/doc/block.md
+++ b/doc/block.md
@@ -9,7 +9,7 @@ Blocks are most commonly used to define functions by including one of the specia
{𝕩+1} 3
×{𝕩𝔽𝕩} 4
-Because they use [lexical scoping](https://en.wikipedia.org/wiki/Scope_(computer_science)#Lexical_scoping), blocks can also be used to encapsulate code. If a block uses only variables that it initializes, then it has no dependence on its environment and would work the same way if defined anywhere. But it can also use external variables, defined in a containing block.
+Because they use [lexical scoping](lexical.md), blocks can also be used to encapsulate code. If a block uses only variables that it initializes, then it has no dependence on its environment and would work the same way if defined anywhere. But it can also use external variables, defined in a containing block.
a←b←"outer"
{ a←"inner" ⋄ a‿b }