Browse thread
Has the thread cancellation problem evolved ?
-
Daniel_Bünzli
-
skaller
- Daniel_Bünzli
- Gerd Stolpmann
- skaller
- Gordon Henriksen
-
skaller
[
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: | 2007-08-27 (23:34) |
From: | Gerd Stolpmann <info@g...> |
Subject: | Re: [Caml-list] Has the thread cancellation problem evolved ? |
Am Sonntag, den 26.08.2007, 01:29 +1000 schrieb skaller: > > [5] by Gerd Stolpmann is > > portable. Note however that neither solution will work with > > uncooperative threads, i.e. those that never perform any system call > > or trigger the gc [7]. > > And it is almost certainly not portable. Portable means on ALL > operating systems .. including Windows. Just reading again what I suggested two years ago. This suggestion is implementable on Windows, as the O'Caml runtime has its own mechanisms to check for asynchronous events (it is needed for switching between threads). Nevertheless, I don't think this is a good thing. Raising an exception at potentially any moment is a problematic thing. E.g. code like let x = try Some(List.assoc ... with _) -> None where the author implicitly assumes that it is only Not_found that can happen and the code is just plain wrong if anything else is encoded into the exception. Gerd -- ------------------------------------------------------------ Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de Phone: +49-6151-153855 Fax: +49-6151-997714 ------------------------------------------------------------