diff options
| author | Rich Hickey <richhickey@gmail.com> | 2007-09-19 12:20:23 +0000 |
|---|---|---|
| committer | Rich Hickey <richhickey@gmail.com> | 2007-09-19 12:20:23 +0000 |
| commit | 2ec1a0d5d2a636c1a4686982c12d5a72a0ea59ce (patch) | |
| tree | 09ae06ffd1161bfe47d43e4627a6a5b386d73cbc /clojure.markdown | |
| parent | 403e49d41871e87d93e030edd6e35aae867eb87c (diff) | |
doc update
Diffstat (limited to 'clojure.markdown')
| -rw-r--r-- | clojure.markdown | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/clojure.markdown b/clojure.markdown index 423817a6..b90254a1 100644 --- a/clojure.markdown +++ b/clojure.markdown @@ -81,7 +81,7 @@ That said, most Clojure programs begin life as text files, and it is the task of One might say the reader has syntax defined in terms of characters, and the Clojure language has syntax defined in terms of symbols, lists, vectors, maps etc. The reader is represented by the function `read`, which reads the next form (not character) from a stream, and returns the object represented by that form. - Since we have to start somewhere, we might as well start where evaluation starts, with the reader forms. This will inevitably entail talking about data structures whose descriptive details, and interpretation by the compiler, will follow. +>Since we have to start somewhere, we might as well start where evaluation starts, with the reader forms. This will inevitably entail talking about data structures whose descriptive details, and interpretation by the compiler, will follow. [hicon]:http://en.wikipedia.org/wiki/Homoiconicity |