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 AAA03550; Wed, 4 Jun 2003 00:43:10 +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 AAA03365 for ; Wed, 4 Jun 2003 00:43:09 +0200 (MET DST) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by nez-perce.inria.fr (8.11.1/8.11.1) with SMTP id h53Mh8T14588 for ; Wed, 4 Jun 2003 00:43:08 +0200 (MET DST) Received: (qmail 26963 invoked from network); 3 Jun 2003 22:43:06 -0000 Received: from arda.pair.com (HELO checkerdell.d6.com) (209.68.1.133) by relay.pair.com with SMTP; 3 Jun 2003 22:43:06 -0000 X-pair-Authenticated: 209.68.1.133 Message-Id: <4.3.2.7.2.20030603153831.030e8a68@localhost> X-Sender: checker@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 03 Jun 2003 15:42:53 -0700 To: Jason Hickey From: Chris Hecker Subject: Re: [Caml-list] ocaml and large development projects Cc: "'caml-list@inria.fr'" In-Reply-To: <3EDD1945.7070701@cs.caltech.edu> References: <4.3.2.7.2.20030602171041.045da898@localhost> <4.3.2.7.2.20030517192812.033d9040@localhost> <4.3.2.7.2.20030602171041.045da898@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam: no; 0.00; hecker:01 checker:01 caml-list:01 ocamlc:01 runnable:01 checksum:01 inlined:01 compiler:01 productive:01 chris:01 ocaml:01 workaround:01 bytecode:01 face:98 handles:01 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk >This is not an issue for the byte-code compiler, ocamlc. Can't you use that? This was covered earlier. My project is a game which has "real time" feedback loops and it just isn't runnable on the bytecode compiler. There's more detail in the archive. The noinline workaround would be fine with me, as I've said before. Or, better yet, some kind of checksum thing that also handles inlined functions and knows when they've changed as well. Both would be the best, because with the former you could completely control when you get a rebuild, and with the latter you can minimize them with no performance penalty. Both useful tools to have at your disposal. >Congrats on the new baby! We just had a new baby too. Thanks, and likewise! Even the power of functional programming has yet to make me productive in the face of this. :) Chris ------------------- 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