aboutsummaryrefslogtreecommitdiff
path: root/docs/doc/extensions.html
diff options
context:
space:
mode:
authorMarshall Lochbaum <mwlochbaum@gmail.com>2020-10-03 16:38:35 -0400
committerMarshall Lochbaum <mwlochbaum@gmail.com>2020-10-03 16:38:35 -0400
commit673de1c627a2046123e1693e9e6508399a028508 (patch)
tree86303316523319eeebcf0e0c52a2be781089c286 /docs/doc/extensions.html
parent8846e63a6f1fe51ee9a68dc511cc6fcdbf54efa6 (diff)
Write files directly from md.bqn, not gendocs (removes trailing empty lines)
Diffstat (limited to 'docs/doc/extensions.html')
-rw-r--r--docs/doc/extensions.html1
1 files changed, 0 insertions, 1 deletions
diff --git a/docs/doc/extensions.html b/docs/doc/extensions.html
index e781194f..08013bc6 100644
--- a/docs/doc/extensions.html
+++ b/docs/doc/extensions.html
@@ -36,4 +36,3 @@
<p>Sometimes it is useful to have a mutable type, particularly if a part of the program should maintain its own state over the course of execution. The <a href="https://en.wikipedia.org/wiki/Closure_(computer_programming)">closures</a> required as part of a complete lexical scoping implementation actually allow something like this. If a function defines and returns an explicit function, then that function can read and change variables in its environment. As the environment includes the scope created to execute the outer function, calling the outer function creates a mutable environment that can be indirectly accessed through the returned function.</p>
<p>A namespace would allow such an environment to be directly accessed and manipulated. While it's possible there would be facilities to create a namespace, a simpler mechanism is simply to add a primitive that returns the current scope as a variable. This scope would then behave the same way as a returned function's environment, and would allow member access by a dot-like syntax.</p>
<p>A symbol is a variable representing a name in the program. Symbols would make it easier to interact with namespaces dynamically.</p>
-