caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Carette <carette@mcmaster.ca>
To: Alain Frisch <alain@frisch.fr>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Working Group: the future of syntax extensions in OCaml, after camlp4
Date: Thu, 24 Jan 2013 13:06:24 -0500	[thread overview]
Message-ID: <51017820.2050201@mcmaster.ca> (raw)
In-Reply-To: <51016AAB.8070403@frisch.fr>

On 13-01-24 12:08 PM, Alain Frisch wrote:
> On 01/24/2013 05:16 PM, rixed@happyleptic.org wrote:
>> Are we interrested here striclty in _pre_processing or is runtime code
>> generation also on topic?
>
> Runtime code generation, and meta-programming a la MetaOCaml are 
> indeed quite a different story, and they are not specifically in the 
> scope of the working group.  I can imagine that some outcomes of this 
> de-camlp4-ifcation might benefit to such projects, though.  For 
> instance, a more liberal concrete syntax (with attributes/quotations) 
> might allow, say,  MetaOCaml, to use directly the official parser, 
> thus avoiding problems related to the fact that it currently needs a 
> custom parser. For instance, I guess that camlp4 extensions cannot be 
> directly used by MetaOCaml users (except if someone decided to port 
> Camlp4 to MetaOCaml). Discussions related to these syntactic aspects 
> are very much welcome in the new mailing list.

I was going to bring this up on the new mailing list, after waiting a 
bit for it to get populated.  I am glad that you intend to keep 
metaocaml-style metaprogramming as 'a different story', as it really is 
exactly that.

Note that the metocaml based on ocaml 3.09 did have a full camlp4 port 
(I did it), but it never worked for the 3.11 version (I tried and did 
not succeed).

Anyways, I've joined the new mailing list, and will participate in such 
a discussion over there.

Jacques

      reply	other threads:[~2013-01-24 18:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-24 14:31 Alain Frisch
2013-01-24 15:52 ` Török Edwin
2013-01-24 15:56   ` Ashish Agarwal
2013-01-24 16:03   ` Esther Baruk
2013-01-24 15:57 ` Daniel Bünzli
2013-01-24 16:24   ` AW: " Gerd Stolpmann
2013-01-28 12:15     ` Alain Frisch
2013-01-28 12:17       ` [wg-camlp4] " Alain Frisch
2013-02-03 14:01       ` AW: " Jon Harrop
2013-02-03 14:38         ` Simon Cruanes
2013-01-24 16:16 ` rixed
2013-01-24 17:08   ` Alain Frisch
2013-01-24 18:06     ` Jacques Carette [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=51017820.2050201@mcmaster.ca \
    --to=carette@mcmaster.ca \
    --cc=alain@frisch.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).