2015-06-02 23:57 GMT+02:00 Daniel Compton <daniel.compton.li...@gmail.com>:
> On the Reader Conditionals > <http://dev.clojure.org/display/design/Reader+Conditionals> dev > discussion page at one part it talks about exception handling: > > "Exception handling, catching "all" - see issue below on why this is not a > complete solution in either case." > > I looked further down the page and couldn't see a discussion of why this > isn't a complete solution. The only mentions of exceptions talked about > them at read time, but not in this context at run time. Is this mentioned > somewhere, on this page or elsewhere? > You're right, there doesn't seem to be any further discussion of this on the page. Probably a Copy&Paste error. I assume, it talks about the issue that in javascript, anything can be thrown, even stuff that doesn't inherit from js/Object. Therefore, to catch really everything, you need to (catch :default ..) in clojurescript. Likewise, in java you need to catch java.lang.Throwable in order to catch everything, though, in most code this is not advisable, since Throwables that are not Exception are used for fatal errors, like OOM conditions. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
