Hello Andrew, Saturday, June 23, 2007, 7:12:52 PM, you wrote:
Is everything described in that paper actually implemented now? (And implemented in exactly the same way as the paper says?)
difference may be in subtle details. it just works for me :)
in my experience, exceptions are rarely required in Haskell program - i use them only to roll out when IO problems occur.
Indeed. Somebody else mentioned Maybe; much cleaner, more intuitive solution.
for me Maybe works great for exclusion of failed items (file not found, etc) while exceptions are used to transfer control over the many calling levels when we need to abort large piece of computation entirely
It's nice that you can have millions of threads if you want to do something very "concurrent". What I tend to want is "parallel" - doing stuff that *could* be done in a single thread, but I want it to go faster using my big mighty multicore box.
this isn't completely different things. threads' easy of use means that you can split your algorithm into parallel tasks here and there, improving CPU utilization
As I understand it, you have to do something "special" to make that happen...?
my own program spend most of its time in C threads, so i can't make exact answer to your query. afair, you need to use -threaded when compiling program, "+RTS -N2" for 2-core box when you run it - that's all. ask me if you need C threads too
While we're on the subject... has anybody ever looked at using muptiple processors on *networked* machines? Haskell's very pure semantics would seem quite well-suited to this...
i'm not sure, but this may be what you are looking for: http://f.loulergue.free.fr/ftp/bsmllib-0.25.tar.gz http://f.loulergue.free.fr/ftp/bsmllib-0.25_manual_html.tar.gz http://www.inf.ufes.br/~ffranzosi/BSPHlib-0.1.tar.gz http://f.loulergue.free.fr/ftp/minibsml-0.11.tar.gz -- Best regards, Bulat mailto:Bulat.Ziganshin@gmail.com