Context Navigation

Changes between Version 75 and Version 76 of Clojure Client Tutorial

-                      v75
+                      v76
 Some advice for Clojure programming:
 * Always strive for pure functions (as in no side effects).  This is critical if you want to avoid refactoring your code later on.
+* Always try to write pure functions (as in no side effects).  This is critical if you want to avoid refactoring your code later on.
 * For tracing functions, use [http://richhickey.github.com/clojure-contrib/trace-api.html].
 * :pre and :post conditions can be used to put constraints on functions.  Here is an example [http://blog.fogus.me/2009/12/21/clojures-pre-and-post].
 …
 * 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.
+* You can often replace global data structures or variables (or classes) with closures.
 * 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.