Re: Pulling threads...

2010-10-30 Thread Brian Ericson
Oh. The "P" in "REPL" makes it non-lazy and the "let" meant that the printer need only print the last line. Ugh. That is completely obvious in hindsight! Thanks! I surrounded a few expressions with "dorun" and now both of my Clojure implementations "run" -- or crawl, given the results of timin

Re: Pulling threads...

2010-10-29 Thread Meikel Brandmeyer
Hi, On 29 Okt., 06:58, Brian Ericson wrote: > (map #(.start %) threads) map is not a loop. It creates a lazy sequences which does - nothing. At least not until it is realised. Here you throw it away immediatelly. Hence, no work is done. Use doseq instead when your main objective are side-effect

Pulling threads...

2010-10-29 Thread Brian Ericson
Please forgive the lengthy post... New to Clojure and trying to get a friend excited about it by demonstrating how Clojure's functional/STM heritage makes it easy to write concurrent/parallel code, but I can't get Clojure to I started with Java, where 256 threads are vying to increment a single c