On 05.06.2009, at 02:48, Howard Lewis Ship wrote: > Again, I'm not sure what the solution is or what the implementation > would look like, but I'd love it if Clojure could relate back to me, > when an exception occurred, what lazy operations were taking place > that caused the bad code to be invoked.
I'd say that's a job for a Clojure-aware debugger, which of course doesn't exist yet. Such a debugger could recognize from the stack trace that the exception was raised in the context of the realization of a lazy sequence. Konrad. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
