I agree with the point in discussion that the error messages in Clojure are more of a problem than stack traces per se.
Regards, Shantanu On Aug 25, 5:02 pm, Nicolas Oury <nicolas.o...@gmail.com> wrote: > I haven't had a lot of problems with stack-traces. > > I would be happy to have more information on the context, though. > > And maybe better reporting of exception occuring in a delayed context. > (when forcing a seq and the excpetion occurs under a lazy.) > In this situation I have sometimes fonud that the stacks where a bit > srange, but I understand it is a well known problem with lazyness and > difficult to solve. > > On Wed, Aug 25, 2010 at 12:54 PM, Peter Schuller > > > > <peter.schul...@infidyne.com> wrote: > > +1 on improving stack traces (though I haven't had experience with > > clj-stacktrace, other than what I have read on this list). > > > -- > > / Peter Schuller > > > -- > > 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 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
