summaryrefslogtreecommitdiff
path: root/clojure.markdown
diff options
context:
space:
mode:
authorRich Hickey <richhickey@gmail.com>2007-09-20 18:34:00 +0000
committerRich Hickey <richhickey@gmail.com>2007-09-20 18:34:00 +0000
commit3c2265abbab40be15976f8945fba4426c468e836 (patch)
treec28183c572aed142fcc40f9e645affbf3dff8ae2 /clojure.markdown
parent98cf7e1cab10a3208c0b60611e9b2b533fbc0eea (diff)
gensym syntax
Diffstat (limited to 'clojure.markdown')
-rw-r--r--clojure.markdown2
1 files changed, 1 insertions, 1 deletions
diff --git a/clojure.markdown b/clojure.markdown
index c3280e09..31d3aa54 100644
--- a/clojure.markdown
+++ b/clojure.markdown
@@ -642,7 +642,7 @@ Thus within-thread bindings obey a stack discipline:
</code></pre>
-Bindings created with `binding` cannot be seen by any other thread. Bindings created with `binding` can be assigned to, which provides a means for nested contexts to communicate up the call stack.
+Bindings created with `binding` cannot be seen by any other thread. Bindings created with `binding` can be assigned to, which provides a means for nested contexts to communicate with code above it the call stack.
Functions defined with `defn` are stored in Vars, allowing for the re-definition of functions in a running program. This also enables many of the possibilities of aspect- or context-oriented programming. For instance, you could wrap a function with logging behavior only in certain call contexts or threads.