On Jan 25, 7:32 pm, Meikel Brandmeyer <m...@kotka.de> wrote: > Hi, > > Disclaimer: I have no clue, what I'm talking about. Just making up > contrived examples, which probably never happen in reality. > > On 25 Jan., 15:13, Ken Wesson <kwess...@gmail.com> wrote: > > > Remember, we're no longer using a "finally" clause, so for the .close > > to be exception-safe *everything* must be caught. But it's rethrown > > unless both threw exceptions, and then we were only ever going to be > > able to keep one exception anyway. > > What should be done, when the body throws an Exception and the close > throws an Error? What happens at the moment when the body throws an > Error and the close throws an Exception?
>From what I know about Java idioms, 'Error' must be upheld at all times because it represents a system-level fault (grave incident), something that cannot be dealt with by the application. For example, OutOfMemoryError is not something that can be generally handled by application and hence must not be swallowed. Regards, Shantanu -- 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
