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 BAA10785; Mon, 29 Mar 2004 01:58:55 +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 BAA09984 for ; Mon, 29 Mar 2004 01:58:54 +0200 (MET DST) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by nez-perce.inria.fr (8.12.10/8.12.10) with ESMTP id i2SNxWKW001160 for ; Mon, 29 Mar 2004 01:59:34 +0200 Received: from [192.168.1.200] (ppp113-158.lns1.syd3.internode.on.net [150.101.113.158]) by smtp1.adl2.internode.on.net (8.12.9/8.12.9) with ESMTP id i2SNwnwn077264; Mon, 29 Mar 2004 09:28:49 +0930 (CST) Subject: Re: [Caml-list] Delaying module initialization From: skaller Reply-To: skaller@users.sourceforge.net To: Jacques Garrigue Cc: skaller@users.sourceforge.net, caml-list In-Reply-To: <20040328193438O.garrigue@kurims.kyoto-u.ac.jp> References: <20040327121832.B29840@pauillac.inria.fr> <406575DA.2090908@socialtools.net> <1080403497.4708.160.camel@pelican.wigram> <20040328193438O.garrigue@kurims.kyoto-u.ac.jp> Content-Type: text/plain Message-Id: <1080518328.4708.181.camel@pelican.wigram> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-4) Date: 29 Mar 2004 09:58:48 +1000 Content-Transfer-Encoding: 7bit X-Miltered: at nez-perce by Joe's j-chkmail ("http://j-chkmail.ensmp.fr")! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; caml-list:01 sourceforge:01 2004:99 jacques:01 sourceforge:01 9660:01 glebe:01 compiler:01 compilers:01 bytecode:01 bytecode:01 garrigue:01 interfaces:01 nsw:01 snail:02 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk X-Status: X-Keywords: X-UID: 401 On Sun, 2004-03-28 at 20:34, Jacques Garrigue wrote: > From: skaller > The main reason I see for wanting dynamic loading of native code is > speed, .. although the bytecode interpreter is apparently quite fast, and for my purposes (a compiler) probably adequate (except for the too small stack size). However I've found the native code more robust, and since the bytecode and native code compilers use *different* binding interfaces to C I felt I had to chose one or the other, and for better or worse I've gone with the native code system. Felix actually works both ways at the moment .. but there is no extensibility yet. -- John Skaller, mailto:skaller@users.sf.net voice: 061-2-9660-0850, snail: PO BOX 401 Glebe NSW 2037 Australia Checkout the Felix programming language http://felix.sf.net ------------------- 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