Yes, this is very important problem with current implementation of Clojure. Many of beginners complain, that they couldn't understand where error happened, especially during compilation of code.
Phil Hagelberg at "Tue, 24 Aug 2010 21:55:52 -0700" wrote: PH> One of the most common complaints about the current implementation of PH> Clojure is that the stack traces are often unreadable. At work we have PH> been using Mark McGranaghan's clj-stacktrace library[1] to print stack PH> traces, and it does a great job of cleaning them up and making it much PH> clearer as to what the actual cause of the problem is. I've found it PH> invaluable for this--it provides indentation, better details, and even PH> coloring to help make the relevant frames stand out in the noise. PH> I've spoken to him about it, and he is agreeable to the idea of PH> merging it into Clojure. He is the sole author of it, and it sounds PH> like he'd be fine with relicensing and copyright assignment. PH> It appears at first glance to be compatible with the existing PH> clojure.stacktrace library. Obviously before it could be merged we PH> would need to investigate this more thoroughly, but I think it could PH> be a valuable improvement to Clojure 1.3. PH> Thoughts? PH> -Phil PH> [1] - http://github.com/mmcgrana/clj-stacktrace -- With best wishes, Alex Ott, MBA http://alexott.blogspot.com/ http://alexott.net http://alexott-ru.blogspot.com/ -- 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
