caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Damien Doligez <damien.doligez@inria.fr>
To: danieljg@sundial.cs.cornell.edu, jgm@cs.cornell.edu,
	pierre.weis@inria.fr
Cc: caml-list@inria.fr
Subject: RE: [Caml-list] Pattern matcher no more supposed to warn on non  exhaustive patterns ?
Date: Thu, 4 Oct 2001 09:36:50 +0200 (MET DST)	[thread overview]
Message-ID: <200110040736.JAA0000032278@beaune.inria.fr> (raw)

>From: "Gregory Morrisett" <jgm@cs.cornell.edu>

>The same thing shows up in SML/NJ with CML.  The problem is that
>in the presence of threads, you really shouldn't be able to=20
>dereference a mutable value in your patterns.

I'd agree that core dump is surprising, but if your multi-threaded
program does anything with a mutable value without the protection of a
mutex, then it is incorrect (i.e. its semantics is unspecified).  In
O'Caml, none of the operations is specified as atomic (except a few
things in the threads library), and you shouldn't assume that they are.

-- Damien
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


             reply	other threads:[~2001-10-04  7:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-04  7:36 Damien Doligez [this message]
2001-10-04  7:51 ` Einar Karttunen
  -- strict thread matches above, loose matches on Subject: below --
2001-10-04  4:29 Gregory Morrisett
2001-10-04  7:06 ` Luc Maranget
2001-10-04  8:17 ` Jacques Garrigue
2001-10-04 12:28 ` Xavier Leroy
2001-10-03 17:37 Jean-Marc Eber
2001-10-03 16:54 ` Dan Grossman
2001-10-03 20:52   ` Pierre Weis
2001-10-04  7:55 ` Luc Maranget
2001-10-04  9:06   ` Luc Maranget

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=200110040736.JAA0000032278@beaune.inria.fr \
    --to=damien.doligez@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=danieljg@sundial.cs.cornell.edu \
    --cc=jgm@cs.cornell.edu \
    --cc=pierre.weis@inria.fr \
    /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).