On May 28, 2013, at 10:32 AM, Rostislav Svoboda wrote: > This might not be the proper example: If (/ 2 n) throws "Divide by > zero" then "n == zero"
Well yes of course it's obvious what the problem is in this case! The point is that if the "bad" function was more complicated then might help to know what value was passed in as n that led to the error. And in more complicated situations it might help to know what args the caller received as well. And what the values of all of the locals were all the way down the stack. What I was describing was just a test to see if LightTable shows the values that args/locals have when an error occurs, and it looks like it doesn't (at least not right out of the box). -Lee -- -- 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/groups/opt_out.
