From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from discorde.inria.fr (discorde.inria.fr [192.93.2.38]) by yquem.inria.fr (Postfix) with ESMTP id 9868FBC69 for ; Sat, 25 Aug 2007 17:44:52 +0200 (CEST) Received: from ipmail01.adl2.internode.on.net (ipmail01.adl2.internode.on.net [203.16.214.140]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id l7PFio7R018893 for ; Sat, 25 Aug 2007 17:44:51 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAAH7lz0Y7pw2h/2dsb2JhbAAM X-IronPort-AV: E=Sophos;i="4.19,307,1183300200"; d="scan'208";a="179328272" Received: from ppp59-167-13-161.lns2.syd7.internode.on.net (HELO [192.168.1.201]) ([59.167.13.161]) by ipmail01.adl2.internode.on.net with ESMTP; 26 Aug 2007 01:14:49 +0930 Subject: Re: [Caml-list] Has the thread cancellation problem evolved ? From: skaller To: Daniel =?ISO-8859-1?Q?B=FCnzli?= Cc: caml-list@yquem.inria.fr In-Reply-To: <9FA25C33-04DD-46BD-8959-873DDD2FFF82@epfl.ch> References: <9FA25C33-04DD-46BD-8959-873DDD2FFF82@epfl.ch> Content-Type: text/plain; charset=utf-8 Date: Sun, 26 Aug 2007 01:44:41 +1000 Message-Id: <1188056681.10796.48.camel@rosella.wigram> Mime-Version: 1.0 X-Mailer: Evolution 2.10.1 Content-Transfer-Encoding: 8bit X-Miltered: at discorde with ID 46D04E72.002 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; 0200,:01 type-safe:01 bytecode:01 sourceforge:01 wrote:01 caml-list:01 linking:02 native:03 native:03 btw:03 raise:03 dynamic:03 daniel:04 problem:05 problem:05 On Sat, 2007-08-25 at 15:58 +0200, Daniel Bünzli wrote: > Hello everybody, > > I would like to raise again the problem of portable thread > cancellation. The potential coming (?) of native dynamic linking > brings the stunning perspective of type-safe, native, plugins. BTW: unrelated issue: unloading the plugins. This presumably will not be possible (since it isn't with bytecode either). ? -- John Skaller Felix, successor to C++: http://felix.sf.net