From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from weis@localhost) by pauillac.inria.fr (8.6.10/8.6.6) id NAA04702 for caml-redistribution; Thu, 15 Feb 1996 13:55:30 +0100 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.6.10/8.6.6) with ESMTP id AAA27873 for ; Thu, 15 Feb 1996 00:37:59 +0100 Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by concorde.inria.fr (8.7.1/8.7.1) with ESMTP id AAA13163 for ; Thu, 15 Feb 1996 00:37:57 +0100 (MET) Received: from boole.logique.jussieu.fr (boole.logique.jussieu.fr [134.157.19.17]) by shiva.jussieu.fr (8.6.10/jtpda-5.1) with ESMTP id AAA04707 ; Thu, 15 Feb 1996 00:37:57 +0100 Received: by boole.logique.jussieu.fr (8.6.10/jtpda-4.0); Thu, 15 Feb 1996 00:38:50 +0100 Date: Thu, 15 Feb 1996 00:38:50 +0100 From: raffalli@logique.jussieu.fr (Christophe Raffalli) Message-Id: <199602142338.AAA06468@boole.logique.jussieu.fr> To: Guy.Cousineau@ens.fr CC: caml-list@pauillac.inria.fr, cousineau@dmi.ens.fr In-reply-to: <9602140923.AA00449@aubepine.ens.fr> (Guy.Cousineau@ens.fr) Subject: Re: Moving from caml Light to CSL Sender: weis Hi, I also faced the problem of having compatibility between CSL and CL. I choosed to use the tool "convert" coming with the distribution. Then if you capitalize your Constructors and record fields in the right way, if you do not use where and limit fun to single case matching, then the result produced by convert seems directly compilable by CSL. So I have only to modify my caml code to respect the above convention and I can produce directly usable CSL code in an automatic way (thanks to convert). This is better than having small functions because, as far as I know there is still no inlining in csl. ---- Christophe Raffalli Dept. of Computer Sciences Chalmers University of Technology URL: http://www.logique.jussieu.fr/www.raffalli