From: "Berke Durak" <berke.durak@gmail.com>
To: "Jon Harrop" <jon@ffconsultancy.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Where's my non-classical shared memory concurrency technology?
Date: Sun, 18 May 2008 10:39:15 +0200 [thread overview]
Message-ID: <b903a8570805180139i7dfe7526u799e82d5126c9f3@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
On Sun, May 18, 2008 at 12:03 AM, Jon Harrop <jon@ffconsultancy.com> wrote:
>
> Avoiding threads does not improve the safety of the language, it simply
> degrades the capabilities of the language.
>
Avoiding threads is like avoiding malloc() in a C program and doing only
static and stack allocation: it is cumbersome and impractical, but avoids a
whole class of allocation bugs.
Similarly, avoiding threads removes concurrency bugs - while reducing the
concurrency capabilities. So it's not really improvement of safety, but
rather avoidance of unsafety - a purely semantic issue.
I think we are still lacking programming language technology to integrate
safe and easy-to-use shared memory concurrency in ML-like languages. Does
anyone know of anything in this area aside from transactional memory?
--
Berke
[-- Attachment #2: Type: text/html, Size: 1100 bytes --]
next reply other threads:[~2008-05-18 8:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 8:39 Berke Durak [this message]
2008-05-18 16:35 ` Jon Harrop
2008-05-19 11:45 ` [Caml-list] " Martin Berger
2008-05-19 12:24 ` Berke Durak
2008-05-19 21:47 ` Jon Harrop
2008-05-19 22:24 ` Berke Durak
2008-05-19 22:37 ` Raoul Duke
2008-05-20 0:04 ` Pierre-Evariste Dagand
2008-05-20 21:27 ` David Teller
2008-05-21 7:52 ` Martin Berger
2008-05-21 8:06 ` Martin Berger
2008-05-19 14:09 ` Gerd Stolpmann
2008-05-19 16:30 ` Richard Jones
2008-05-19 18:26 ` Jon Harrop
2008-05-20 7:40 ` Ulf Wiger (TN/EAB)
2008-05-21 8:18 ` Martin Berger
2008-05-21 8:06 ` Martin Berger
2008-05-21 13:50 ` Gerd Stolpmann
2008-05-26 15:29 ` Damien Doligez
2008-05-26 16:08 ` Jon Harrop
2008-05-27 9:34 ` Martin Berger
2008-05-28 11:18 ` Damien Doligez
2008-05-28 12:16 ` Jon Harrop
2008-05-28 17:41 ` Martin Berger
2008-05-29 12:02 ` Frédéric Gava
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=b903a8570805180139i7dfe7526u799e82d5126c9f3@mail.gmail.com \
--to=berke.durak@gmail.com \
--cc=caml-list@inria.fr \
--cc=jon@ffconsultancy.com \
/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).