Changes between Version 65 and Version 66 of Clojure Client Tutorial

Timestamp:

Aug 22, 2011 11:44:03 AM (13 years ago)

Author:

kedwar10

Comment:

--

Clojure Client Tutorial

@@ -30 +30 @@
 
 Lisp and Scheme resources:
-* The Little/Seasoned/Reasoned Schemer (very gentle introduction to scheme).
+* The Little / Seasoned / Reasoned Schemer (gentle introductions to scheme).
 * How To Design Programs [[http://www.htdp.org/]] (introduction to scheme and programming).
 * Paradigms of Artificial Intelligence Programming: Case Studies in Common Lisp, by Peter Norvig (introduction to lisp and AI).
@@ -43 +43 @@
 * If you define a record in a namespace and wish to access it in another, you must explicitly import it with the ":import" keyword in your namespace declaration.
 * Giving names to your anonymous functions will dramatically increase the usefulness of clojure error reporting (an example: (fn identity [x] x).  Doing this will also allow the function to call itself.
-* If you want to ensure tail cail optimization, use the "recur" function instead of using your function name.  "recur" also works with loops.
+* If you want to ensure tail-call optimization, use the "recur" function instead of using your function name.  "recur" also works with loops.
 * "Weird" error messages usually result from forgetting to specify the arguments during a function definition or from mismatched parenthesis.
-* Atoms are your go-to way to manage state.
-* The function that you pass as an argument to swap! must be pure.  This is because the update to the atom is retriable so it may get called more then once.
+* Atoms are your go-to way to manage state.  (Don't ignore the other types however, as choosing the inappropriate type can force a refactoring later on.)
+* The function that you pass as an argument to "swap!" (the function that updates an atom) must be pure.  This is because the update to the atom is retriable so it may get called more then once.
 * If you must define a type, prefer the simplest option.  A decision flowchart: [http://cemerick.com/2011/07/05/flowchart-for-choosing-the-right-clojure-type-definition-form/].
 * If a future fails silently, try just running your function in a regular thread instead.