A couple more replies to comments on this thread:

On May 28, 2013, at 5:50 PM, Cedric Greevey wrote:
> 
> Clojure just doesn't make what he asked for easy, by its nature. Designing to 
> minimize difficulty with reproducing any observed behavior seems to be 
> indicated (and desirable for other reasons anyway).

Sure, but in some kinds/styles of work this is more inconvenient / 
inappropriate than in others.


On May 28, 2013, at 6:08 PM, Sean Corfield wrote:
> 
> Mark's original point is well-made: the biggest "bang for our buck" is
> likely to come from exceptions being able to capture and automatically
> display all of the in-scope vars at the point of failure. Even with a 
> step debugger, you still have to reproduce the failure, often [etc]


I agree 100% with Sean and Mark that, from my perspective, the best thing to 
shoot for is some kind of display of locals at the point of an error. This was 
always crucial to me in Common Lisp (I never much used the stepper or the 
snazzy restart mechanism) and its absence in Clojure has been one of the main 
pain points of my transition to Clojure. I think this is true of my work as a 
programmer/researcher but also as a teacher; when something breaks, which is 
all the time with new programmers, you want to be able to look around and see 
what the state was that caused the error. You really want to see the values of 
locals, and in Common Lisp that was easy and obvious, while in Clojure it seems 
to be close to impossible.

It looks from Hugo's video like I can get this kind of functionality now if I 
run my code via emacs and use nrepl-ritz... although it sounds like this can 
lead to memory management problems, so that one shouldn't do it routinely (and 
plus I generally want to run my code in other ways). So, not optimal but a 
start. If there was a way to get locals to be displayed on error, without the 
restriction to emacs and without the performance issues, then I think that 
would be a big win for a lot of people.

 -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.


Reply via email to