From: Florian Hars <florian@hars.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] calling native code from bytecode?
Date: Thu, 9 Aug 2001 08:57:52 +0200 [thread overview]
Message-ID: <20010809085752.A6270@hars> (raw)
In-Reply-To: <20010808104615.A3590@pauillac.inria.fr>; from Xavier.Leroy@inria.fr on Wed, Aug 08, 2001 at 10:46:15AM +0200
On Wed, Aug 08, 2001 at 10:46:15AM +0200, Xavier Leroy wrote:
> My advice is: don't do it. If all you need is to have the
> efficiency of native code and the debugging comfort of bytecode, just
> compile all your sources twice, to native-code and to bytecode.
Or debug by insterting print statements in the native code. This is
what I did, once the first part of the code worked (which takes about
30 to 40 seconds if compiled natively). Waiting five minutes to debug
every new function is no fun...
Yours, Florian Hars.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-08-09 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-01 23:45 Chris Hecker
2001-08-03 12:03 ` Xavier Leroy
2001-08-03 14:31 ` Chris Hecker
2001-08-08 8:46 ` Xavier Leroy
2001-08-08 18:34 ` Chris Hecker
2001-08-09 6:57 ` Florian Hars [this message]
2001-08-14 13:34 ` Fabrice Le Fessant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20010809085752.A6270@hars \
--to=florian@hars.de \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox