caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Remi VANICAT <vanicat@labri.u-bordeaux.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] ANN: Dynamic Caml v0.2 is released
Date: 16 May 2002 14:20:25 +0200	[thread overview]
Message-ID: <ya3d6vwz3li.dlv@serveur3.labri.fr> (raw)
In-Reply-To: <Pine.LNX.4.21.0205161620150.28281-100000@oops.tepkom.ru>

Dmitry Lomov <dsl@intellij.com> writes:

> I am pleased to announce the availability of Dynamic Caml v.0.2
> from:
> 
> http://oops.tercom.ru/dml/
> 
> Dynamic Caml is a high-level, type-safe (statically typed)
> and efficient dynamic code generation library and a set of 
> CamlP4 syntax extensions for Objective Caml. 
> 
> Though still supporting only bytecode,
> release 0.2 is much more mature than the previous 0.1 release.

I've a question about the link betwen Dynamic Caml and MetaOCaml 
(you can found MetaOcaml at
http://cs-www.cs.yale.edu/homes/taha/MetaOCaml/) 

As I see it, the main difference is that MetaOcaml is a modification
of the ocaml compiler, and dml is an external library, but is there
any more in depth difference between the two ? (By the way, MetaOCaml
lack a good documentation).

But it seem also (I may be wrong) that MetaOCaml enable more easily
multi stage generation (that is program that generate program that
generate program) Is this feasible with dml ?
-- 
Rémi Vanicat
vanicat@labri.u-bordeaux.fr
http://dept-info.labri.u-bordeaux.fr/~vanicat
-------------------
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:[~2002-05-16 12:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-16 12:40 Dmitry Lomov
2002-05-16 12:20 ` Remi VANICAT [this message]
2002-05-21 20:05   ` Dynamic Caml vs. MetaOCaml [long] (Was: Re: [Caml-list] ANN: Dynamic Caml v0.2 is released) Dmitry Lomov

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=ya3d6vwz3li.dlv@serveur3.labri.fr \
    --to=vanicat@labri.u-bordeaux.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).