Gary Trakhman <gary.trakh...@gmail.com> writes: > Knowing with certainty that some called method is defined above in the > compilation strategy simplifies code-reading and comprehension by > minimizing where you have to look, and it also makes it easier to move > stuff around with a text editor than what I imagine the alternative > would provide.
I never really care about backward or forward when jumping about code. The editors take care of it for me. > I haven't used a late-binding lisp in a large code-base, so I'm contrasting > against my experience with Java. It's a total pain in the ass. You write some lisp, start to debug it carefully, and half way through hit a mispelt symbol. (defun thing[fred x] (funcall frd x)) In Clojure, the closest equivalent (hitting a symbol you have declared, but not defined) is rare: (declare frd) (defun thing[fred x] (frd x)) Although, pre-declaration doesn't prevent a related bug which is using a symbol that you *think* is local but is actually global as in: (defn blah [mp] (do-stuff-to map)) Having said this this, having to declare things first and being forced to write bottom up is also a pain. Win some, lose some. Phil -- 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 --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
