From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id KAA03232 for caml-redistribution; Wed, 10 Mar 1999 10:25:07 +0100 (MET) Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id KAA26575 for ; Wed, 10 Mar 1999 10:19:54 +0100 (MET) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by concorde.inria.fr (8.8.7/8.8.7) with ESMTP id KAA08820; Wed, 10 Mar 1999 10:19:50 +0100 (MET) Received: (from xleroy@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id KAA14124; Wed, 10 Mar 1999 10:19:50 +0100 (MET) Message-ID: <19990310101949.08839@pauillac.inria.fr> Date: Wed, 10 Mar 1999 10:19:49 +0100 From: Xavier Leroy To: "Frank A. Christoph" , caml-list@inria.fr Subject: Re: No ThreadUnix.select in systhreads References: <007601be6a36$b1ab89e0$6f50ebca@newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1 In-Reply-To: <007601be6a36$b1ab89e0$6f50ebca@newton>; from Frank A. Christoph on Tue, Mar 09, 1999 at 11:11:12PM +0900 Sender: weis > The threadUnix.mli in otherlibs/systhreads lacks the function > "select" which appears in otherlibs/threads/threadUnix.mli. Is this > intentional? I fixed this by just adding > let select = Thread.select It's an oversight. Your fix is correct. - Xavier Leroy