From: Jacques Carette <carette@mcmaster.ca>
To: Jon Harrop <jonathandeanharrop@googlemail.com>
Cc: Nicolas Pouillard <nicolas.pouillard@gmail.com>,
caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: Metaprogramming features
Date: Tue, 07 Oct 2008 12:31:01 -0400 [thread overview]
Message-ID: <48EB8EC5.30304@mcmaster.ca> (raw)
In-Reply-To: <200810071636.43288.jon@ffconsultancy.com>
Jon Harrop wrote:
> So the translation from MetaOCaml to OCaml is not obvious at all.
>
> This begs the question: could another formulation of MetaOCaml avoid these
> complications without losing expressiveness?
>
No. See some of the early papers of Taha and papers from Sheard around
the same time.
BTW, F#'s metaprogramming features are much much less powerful than
metaocaml's. We tried to use them to generalize some previous work I
(with some other colleagues) had done in metaocaml, but couldn't.
Essentially, F#'s splices are first-order only.
Jacques
next prev parent reply other threads:[~2008-10-07 16:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 14:34 Jacques Carette
2008-10-03 15:09 ` [Caml-list] " Dario Teixeira
2008-10-04 2:00 ` Jon Harrop
2008-10-04 9:03 ` David Teller
2008-10-04 14:22 ` Jon Harrop
2008-10-06 14:06 ` Brian Hurt
2008-10-06 15:56 ` Jon Harrop
2008-10-06 16:46 ` Chung-chieh Shan
2008-10-07 0:17 ` [Caml-list] " Jon Harrop
2008-10-07 12:49 ` Nicolas Pouillard
2008-10-07 15:36 ` Jon Harrop
2008-10-07 16:31 ` Jacques Carette [this message]
2008-10-03 16:01 ` [Caml-list] " David Teller
2008-10-03 21:14 ` Paolo Donadeo
2008-10-04 2:17 ` Jon Harrop
2008-10-04 9:10 ` David Teller
2008-10-04 0:49 ` Stefano Zacchiroli
2008-10-04 2:03 ` Jon Harrop
2008-10-04 8:23 ` Richard Jones
2008-10-04 14:31 ` Jon Harrop
2008-10-04 13:57 ` Richard Jones
2008-10-04 19:41 ` Jon Harrop
2008-10-04 19:04 ` Richard Jones
2008-10-05 1:05 ` Jon Harrop
2008-10-06 16:54 ` Chung-chieh Shan
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=48EB8EC5.30304@mcmaster.ca \
--to=carette@mcmaster.ca \
--cc=caml-list@yquem.inria.fr \
--cc=jonathandeanharrop@googlemail.com \
--cc=nicolas.pouillard@gmail.com \
/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).