Exactly. Not only debugging, but java interop that involved calling methods with side effects.
On Thursday, 18 October 2012 15:02:47 UTC-4, David Nolen wrote: > > On Thu, Oct 18, 2012 at 2:55 PM, Alan Malloy <al...@malloys.org<javascript:> > > wrote: > >> It's rare to get tired of this, because nobody does it: it's not >> common because your interleaved statements are side-effecting only, >> which is not encouraged in Clojure, and rarely needed. Certainly >> sometimes it's the best way to do something, but not so often that I'd >> become frustrated; if anything, having to write such irritating code >> can serve as a good reminder that I shouldn't have so many >> unrestrained side effects scattered through my logic. > > > I think from the examples debugging via print statements was the main (and > reasonable) use case. > > David > -- 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
