"Steve Molitor" <stevemoli...@gmail.com> wrote: >> The Python approach leads to more readable >>code: http://www.mired.org/home/mwm/papers/readability.html > >The two cases he sites do not apply to Clojure:
More accurately, the problem being analyzed (a variable changing to a bad value) can't happen in clojure. It has to have been bound with a bad value. >The first case is a function that is allowed to change the value of a >variable passed into it. Variables are immutable in Clojure so you can't >write the dangerous 'inc' function he describes. You can't change the value >of a variable passed to a function in Python either, but you can pass a >mutable object to a function and have the function modify the object, which >is close to the same thing. Clojure is much more readable than Python in >this regard. You might also note that lisp behaves the same way as python - at least outside of macros. As noted in the last paragraph, the paper isn't about lisp vs other languages, its about readability vs "power as terseness". The examples just happened to pick on a feature heavily associated with lisp. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en
