On 03.01.2009, at 21:20, Mark Volkmann wrote:
> One of the stated benefits of functional programming I've seen is that
> the compiler of a functional language can analyze code and determine
> statements within a function
> that can safely be run concurrently. As
> far as I know Clojure doesn't ye
On Jan 3, 9:53 pm, Brian Will wrote:
> > Remember that "parallel" and "concurrent" are two different things.
> > "Concurrent" is something you deal with all the time if you are
> > writing GUI apps: there are different threads and they interact in
> > some possibly unpredictable way. You can ha
> Remember that "parallel" and "concurrent" are two different things.
> "Concurrent" is something you deal with all the time if you are
> writing GUI apps: there are different threads and they interact in
> some possibly unpredictable way. You can have concurrency on a single-
> core machine. "
On Jan 3, 2:08 pm, Brian Will wrote:
> http://en.wikipedia.org/wiki/Automatic_parallelization
The article looks out-of-date and inaccurate, alas...
mfh
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Clojure" gr
On Jan 3, 12:20 pm, "Mark Volkmann" wrote:
> One of the stated benefits of functional programming I've seen is that
> the compiler of a functional language can analyze code and determine
> statements within a function
that can safely be run concurrently. As
> far as I know Clojure doesn't yet do
Clojure doesn't start any threads you don't tell it to.
In Haskell, there's a strict compile-time distinction between pure
functions and impure functions, so Haskell always knows which
functions can be run concurrently without issue. Actually running
stuff concurrently without explicit direction
