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 RAA15391 for caml-red; Fri, 9 Feb 2001 17:00:15 +0100 (MET) Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id NAA29265 for ; Fri, 9 Feb 2001 13:01:17 +0100 (MET) Received: from mail4.microsoft.com (mail4.microsoft.com [131.107.3.122]) by nez-perce.inria.fr (8.11.1/8.10.0) with SMTP id f19C1GL24372 for ; Fri, 9 Feb 2001 13:01:16 +0100 (MET) Received: from 157.54.9.103 by mail4.microsoft.com (InterScan E-Mail VirusWall NT); Fri, 09 Feb 2001 01:48:45 -0800 (Pacific Standard Time) Received: by inet-imc-04.redmond.corp.microsoft.com with Internet Mail Service (5.5.2653.19) id <1TB072CN>; Fri, 9 Feb 2001 01:47:25 -0800 Message-ID: <112C6E8A1B25D34BB27D48D2FD2E96CFC942C0@TVP-MSG-02.europe.corp.microsoft.com> From: Claudio Russo To: Brian Rogoff , caml-list@inria.fr Subject: RE: first class, recursive, mixin modules (was: RE: first class m odules) Date: Fri, 9 Feb 2001 01:41:06 -0800 X-Mailer: Internet Mail Service (5.5.2653.19) content-class: urn:content-classes:message Sender: weis@pauillac.inria.fr > On Fri, 12 Jan 2001, Claudio Russo wrote: > > I wasn't quite sure of your intention, but I did get the > attached code > > to work in Mosml (it includes a port of the Ocaml libraries and a > > fleshed out implementation of your idea). > > Cool! OK, now Alain has at least one example of a practically > useful case > handled by your scheme :-). I suspect that this problem bites > lots of ML > programmers, and a fix is eagerly desired by at least two OCaml > programmers. Congratulations on making this work, the millenium is > starting off on a great note already! I'm not really sure it bites that many, but I'd like to be told otherwise. It does really hit you when trying to implement Chris Okasakis elegant bootstrapped data structures, or emulate object oriented things with modules. (Together with first-class and recursive structure, you can model quite a bit of object oriented stuff, but I'm not sure how natural or efficient this appproach is.) > > Unfortunately, this only works in an internal release of > Moscow, because > > of a (known) bug in the current distribution. > > Well, even more unfortunately, a fix in Mosml doesn't help me > unless you > change to Mosocaml. I couldn't switch to SML even if I wanted > to, and I > don't want to! Hopefully the OCaml Implementors (you guys are even > capitalized now) will "borrow back" the Mosml improvements > into OCaml. If I had the time, I'd do it, but I don't really. It should be easy to deconstruct the Moscow ML sources and transplant the ideas to Ocaml (at least to the bytecode interpreter). I can give pointers to whoever tries to do that. Cheers, Claudio >