Gary Verhaegen, thanks for that. The idea of buffers and threads dying is a good one and gives me something to look for.
On Monday, October 9, 2017 at 2:23:05 PM UTC-4, lawrence...@gmail.com wrote: > > MatchingSocks, thanks for that. I think the pattern I followed everywhere > was: > > (future > (slingshot/try+ > ;;; some code > (catch Object o > (println o)))) > > So I think I do catch everything inside of each future that I launch. But > I will check again. Perhaps I missed one somewhere. > > > On Monday, October 9, 2017 at 8:12:33 AM UTC-4, Matching Socks wrote: >> >> The linked page >> https://stuartsierra.com/2015/05/27/clojure-uncaught-exceptions also >> says "Another wrinkle: exceptions inside a future are always caught by the >> Future. The exception will not be thrown until something calls Future.get >> (deref in Clojure)." So you would need to review the pattern of "(try >> (future (catch (throw". >> > -- 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.
