Browse thread
RE: [Caml-list] Pattern matcher no more supposed to warn on non exhaustive patterns ?
- Damien Doligez
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: | 2001-10-04 (07:36) |
From: | Damien Doligez <damien.doligez@i...> |
Subject: | RE: [Caml-list] Pattern matcher no more supposed to warn on non exhaustive patterns ? |
>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