caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Basile Starynkevitch [local]" <basile.starynkevitch@inria.fr>
To: James Leifer <James.Leifer@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] mod_caml's bytecode restriction due to Apache or just CGI dyn'linking?
Date: Mon, 21 Jun 2004 09:51:47 +0200	[thread overview]
Message-ID: <20040621075147.GA29516@bourg.inria.fr> (raw)
In-Reply-To: <r77wu21bc1o.fsf@muscadet.inria.fr>

On Mon, Jun 21, 2004 at 09:33:23AM +0200, James Leifer wrote:
> "Basile Starynkevitch [local]" <basile.starynkevitch@inria.fr> writes:
> 
> > Sorry for the shameless plug - but I think that ocamljit can be used
> > to accelerate a bit such Ocaml propulsed web pages.
> 
> So, ocamljit plays well with dynamic .cmo linking?

Yes, it was designed to mimic as much as possible the bytecode interpreter.

The main misfeature of ocamljit is lack of [ocaml] debugger support -
because the few debug related bytecodes are not supported by it (in
the case yu run into them, you got a loud fatal error!)

-- 
Basile STARYNKEVITCH -- basile dot starynkevitch at inria dot fr
Project cristal.inria.fr - phone +33 1 3963 5197 - mobile 6 8501 2359
http://cristal.inria.fr/~starynke --- all opinions are only mine 

-------------------
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


      reply	other threads:[~2004-06-21  7:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-20 21:38 James Leifer
2004-06-20 23:07 ` Richard Jones
2004-06-21  7:18   ` James Leifer
2004-06-21  4:46 ` Basile Starynkevitch [local]
2004-06-21  7:33   ` James Leifer
2004-06-21  7:51     ` Basile Starynkevitch [local] [this message]

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=20040621075147.GA29516@bourg.inria.fr \
    --to=basile.starynkevitch@inria.fr \
    --cc=James.Leifer@inria.fr \
    --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;
as well as URLs for NNTP newsgroup(s).