From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id TAA23982; Thu, 26 Aug 2004 19:09:48 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f 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 TAA19590 for ; Thu, 26 Aug 2004 19:09:47 +0200 (MET DST) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.86]) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id i7QH9k5F012676 for ; Thu, 26 Aug 2004 19:09:46 +0200 Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id i7QH9Tao023571; Thu, 26 Aug 2004 10:09:29 -0700 (PDT) Received: from [192.168.1.100] (dsl081-080-123.lax1.dsl.speakeasy.net [64.81.80.123]) (authenticated bits=0) by mac.com (Xserve/smtpin07/MantshX 4.0) with ESMTP id i7QH9PM0017354; Thu, 26 Aug 2004 10:09:27 -0700 (PDT) In-Reply-To: References: <1093514139.15255.692.camel@pelican.wigram> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit Cc: caml-list@inria.fr From: Paul Snively Subject: Re: [Caml-list] Re: bytecode and native code at once Date: Thu, 26 Aug 2004 10:09:02 -0700 To: mikel X-Pgp-Agent: GPGMail 1.0.2 X-Mailer: Apple Mail (2.619) X-Miltered: at nez-perce with ID 412E195A.001 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; caml-list:01 hash:01 doable:01 coexist:01 runtime:01 closures:01 asmdynlink:01 metaocaml:01 metaocaml:01 bug:01 faq:01 faq:01 beginner's:01 beginners:01 1.2.4:01 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Mikel! On Aug 26, 2004, at 8:52 AM, mikel wrote: > It's doable in principle. For example, the old MacScheme compiler used > parameters to tune compilation on a per-function basis; low > optimization settings resulted in generation of bytecode; high > optimization settings resulted in generation of native code. Both > types of function could coexist in the same runtime, with the > different kinds of closures represented by different appliable types. > > I don't know what implications such a scheme might have for type > safety in Ocaml. > Is there some reason that asmdynlink, which is part of the Caml Development Kit, doesn't address this? I also think that once MetaOCaml gets its native compiler done that it will help answer the question as well, among others. I find MetaOCaml very exciting! > ------------------- > To unsubscribe, mail caml-list-request@inria.fr Archives: > http://caml.inria.fr > Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: > http://caml.inria.fr/FAQ/ > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Best regards, Paul -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iEYEARECAAYFAkEuGUEACgkQbot1wzHBQBVg0ACbB4ho0nrAjFy4rn/bQ6DMYv4f TH8AnAmwIqi8gjd+52R/skPrGpPhNd3A =Dqkn -----END PGP SIGNATURE----- ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners