caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Asfand Yar Qazi <email@asfandyar.cjb.net>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] STM support in OCaml
Date: Thu, 09 Mar 2006 11:36:51 +1100	[thread overview]
Message-ID: <1141864611.23909.164.camel@budgie.wigram> (raw)
In-Reply-To: <440F6275.90301@asfandyar.cjb.net>

On Wed, 2006-03-08 at 23:02 +0000, Asfand Yar Qazi wrote:

> To tell the truth, I just want to be on the bleeding edge - hence my desire to 
> get away from this horrid imperative programming I've been indoctrinated with, 
> and to learn how to get the most out of tomorrows processors, which will all 
> be multi-core.

hehe .. but procedural programming IS the bleeding edge now.

> (according to Tim Sweeny anyway) STM allows writing 
> multithreaded apps "almost as easily as single threaded ones", so would be the 
> solution to the headaches one normally associates with concurrent programming.

Yes, I tend to feel this is so, because it provides composition.
Another way of doing this is to use channels. As a programmer
I'd like a choice of techniques .. so I'd like both (and locks
as well .. just in case. I still use 'goto' :)

You can try out channels in Ocaml, see the Event module.
This is also 'lock free' in the sense the programmer
writes no locks. You also have composition, but a different
kind to STM (in fact, almost looks like they're dual/control
inverse).

-- 
John Skaller <skaller at users dot sourceforge dot net>
Async PL, Realtime software consultants
Checkout Felix: http://felix.sourceforge.net


  reply	other threads:[~2006-03-08 23:56 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-08 10:11 yoann padioleau
2006-03-08 10:41 ` Asfand Yar Qazi
2006-03-08 12:23   ` skaller
2006-03-08 23:02     ` Asfand Yar Qazi
2006-03-09  0:36       ` skaller [this message]
2006-03-08 11:32 ` Gerd Stolpmann
2006-03-08 12:04   ` skaller
2006-03-08 19:22     ` Dan Grossman
2006-03-08 22:10       ` skaller
  -- strict thread matches above, loose matches on Subject: below --
2006-03-07 16:18 Asfand Yar Qazi
2006-03-07 16:50 ` [Caml-list] " Sebastian Egner
2006-03-07 17:44   ` Michael Hicks
2006-03-08  0:37     ` Asfand Yar Qazi
2006-03-08  5:05       ` Erick Tryzelaar
2006-03-07 17:15 ` skaller
2006-03-07 19:05   ` Asfand Yar Qazi
2006-03-08  0:52     ` skaller
2006-03-08 10:38       ` Asfand Yar Qazi
2006-03-08 19:36       ` William Lovas
2006-03-08 20:45         ` Brian Hurt
2006-03-08 21:14           ` Paul Snively
2006-03-08 22:06           ` skaller
2006-03-08 22:10             ` Gerd Stolpmann
2006-03-08 23:48               ` skaller
2006-03-09  7:45               ` Andrae Muys
2006-03-09  9:18                 ` David Brown
2006-03-08 22:11             ` Brian Hurt
2006-03-08 23:05               ` Lodewijk Vöge
2006-03-09  3:13                 ` Brian Hurt
2006-03-08 23:45               ` Robert Roessler
2006-03-09  0:23               ` skaller
2006-03-09  3:19                 ` Brian Hurt
2006-03-09  4:32                   ` skaller
2006-03-09 10:38                     ` John Chu
2006-03-11 15:26             ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1141864611.23909.164.camel@budgie.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@yquem.inria.fr \
    --cc=email@asfandyar.cjb.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).