Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Hendrik Boom <hendrik@topoi.pooq.com>
To: caml-list@inria.fr
Subject: [Caml-list] campp{4,5} and ppx
Date: Mon, 26 Oct 2015 19:50:37 -0400	[thread overview]
Message-ID: <20151026235037.GA29951@topoi.pooq.com> (raw)
In-Reply-To: <CAPFanBGCcfOPVYWZtm1zya5rKU4VNzi=enxy54iKn+bfPYd-7g@mail.gmail.com>

On Mon, Oct 26, 2015 at 04:30:39PM +0100, Gabriel Scherer wrote:
> To my knowledge, nobody has contributed parsing of attributes and
> extensions (a change to the OCaml syntax whose use is central to many of
> the ppx extensions) to camlp4 or camlp5 (which implement their own OCaml
> parsers and thus need to be updated accordingly). It would not necessarily
> be too difficult to do so, but that means that currently you cannot combine
> camlp{4,5} and PPX extensions within the same source file.

Presumabbly ther qould be no problem if the camlp{4,5} and the PPX 
extensions were used in different source files?

> 
> There is another way to understand your question: if you have developed
> camlp{4,5} extensions, how hard is it to port them to ppx, or conversely to
> port a ppx extension to camlp{4,5}? My answer would be "rather easy",
> knowing that there are two separate aspects:

This invites another question:

How many of the things made available in camlp{4,5}, such as stream 
parsers, have been ported to ppx?

-- hendrik

  reply	other threads:[~2015-10-26 23:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-26 13:35 [Caml-list] Is this the right place to discuss camlp5? Soegtrop, Michael
2015-10-26 13:40 ` Gabriel Scherer
2015-10-26 14:01   ` Soegtrop, Michael
2015-10-26 14:21 ` Hendrik Boom
2015-10-26 14:27   ` David Allsopp
2015-10-26 15:18     ` Hendrik Boom
2015-10-26 15:30       ` Gabriel Scherer
2015-10-26 23:50         ` Hendrik Boom [this message]
2015-10-26 14:29   ` Ashish Agarwal

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=20151026235037.GA29951@topoi.pooq.com \
    --to=hendrik@topoi.pooq.com \
    --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