On Mon, May 23, 2011 at 1:28 PM, Daniel Werner <daniel.d.wer...@googlemail.com> wrote: > On May 23, 12:24 am, Aaron Bedra <aaron.be...@gmail.com> wrote: >> Have you signed a CA yet? If so, you can sign up for a confluence account >> and start a wiki page around this. This way the appropriate discussions and >> review can take place and then possibly a JIRA ticket/patch to fix things >> up. > > Discussions about improving Clojure error handling are already under > way: > > http://dev.clojure.org/display/design/Error+Handling
Hmm. > The RuntimeException wrapping problem seems not to have been brought > up yet, though. It would be simple, backward compatible with code that catches (or lets slip) RuntimeException, and a substantial improvement to create a ClojureRuntimeException subclass of RuntimeException and add a function to core that takes an exception and, if it's a ClojureRuntimeException instance, recurses down the .getCause() chain until it isn't and then returns it. This would return the outermost exception generated by an API and not wrapped by Clojure HOFs. -- Protege: What is this seething mass of parentheses?! Master: Your father's Lisp REPL. This is the language of a true hacker. Not as clumsy or random as C++; a language for a more civilized age. -- 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
