On Jan 29, 10:36 am, kyle smith <the1physic...@gmail.com> wrote: > I have improved on chouser'sgviewcode (http://blog.n01se.net/? > p=30). It can now expand java.awt.Container objects.
Just for kicks I've expanded to handle Exceptions http://groups.google.com/group/clojure/web/gview.clj user=> (gview/gview *e) Of course it doesn't really help much because the Exception doesn't contain any of the juicy stuff like the form that caused the exception or any 'variables'. So I tried JSwat, but I can't figure out how one can 'explore' the last exception *e... everything is connected up but I guess it expects breakpoints or something, which while useful is not what I think I'm trying to achieve. It occurred to me that it might not be so hard to get the form that the exception occurred upon, all clojure exceptions would simply need to derive from an exception that took the form it occured on (which is available in RT). I'd say this over encoding it in the message because the form can sometimes be large. Now with this info you could have a more full featured interactive diagnostic. It might even be possible to capture the value of symbols in the form... Any thoughts/tips? Regards, Tim. --~--~---------~--~----~------------~-------~--~----~ 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 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 -~----------~----~----~----~------~----~------~--~---
