[m-users.] spawn in Rosettacode
robert.kenneth.smart at gmail.com
Fri Aug 29 13:29:03 AEST 2014
At http://rosettacode.org/wiki/Concurrent_computing#Mercury, we see:
It is a bit hard to understand how this could work. My beginner's
understanding would be that the 2nd spawn couldn't happen till the first
had produced the new world that is its input parameter. Etc.
And my compilation of it (on OSX) produces the outputs in the same order as
in the program every time.
It is interesting to consider how languages which explicitly thread IO
(like Haskell and Mercury) should handle multiple interactions with the
world where the order doesn't matter, so that concurrency can be done
implicitly or explicitly.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users