From: Alain Frisch <alain@frisch.fr>
To: Hongbo Zhang <bobzhang1988@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Re: Syntax extensions without Camlp4
Date: Wed, 30 May 2012 14:41:57 +0200 [thread overview]
Message-ID: <4FC61595.6070009@frisch.fr> (raw)
In-Reply-To: <jptm5g$bul$1@dough.gmane.org>
On 05/27/2012 06:53 PM, Hongbo Zhang wrote:
> Well, I don't think it's good to downplay camlp4. The problem is we need
> more documentation and more tests.
(The new) Camlp4 has been here for several years. Documentation and
tests are still lagging behind. Nevertheless, it burns a non-negligible
fraction of the total resource spent by maintainers on OCaml (fixing
bugs, struggling with camlp4 to take new language features into account).
In addition, there is a growing consensus that the most common uses of
camlp4 (such as code generation driven by type declaration) might be
based on a much simpler approach, and this would actually have
advantages for the end-users (like not changing the concrete syntax)
and for developers (much less information to grasp in order to write
such an extension).
Coq is one of the few examples of a big project that relies on other
aspects of camlp4 (e.g. its parsing framework with extensible grammars).
As far as I know, it also still works with camlp5, which is actively
maintained, and I don't believe the Coq guys enjoy so much maintaining
support for both camlp4 and campl5.
All that considered, and this is only a personal opinion: I don't see
compelling arguments to continue investing efforts in camlp4 itself (at
least, for the core OCaml team) and I believe it is a good time to start
considering a (medium-term) future of OCaml without camlp4. Of course,
alternative solutions need to be developed and streamlined before
killing camlp4 is even considered.
Alain
next prev parent reply other threads:[~2012-05-30 12:42 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-27 15:06 [Caml-list] " Alexandre Pilkiewicz
2012-05-27 16:53 ` [Caml-list] " Hongbo Zhang
2012-05-27 18:04 ` Daniel Bünzli
2012-05-27 18:18 ` Hongbo Zhang
2012-05-27 19:01 ` Daniel Bünzli
2012-05-27 22:43 ` Wojciech Meyer
2012-05-28 9:35 ` Daniel Bünzli
2012-05-28 9:59 ` Gabriel Scherer
2012-05-30 14:45 ` Hongbo Zhang
2012-05-28 11:17 ` Wojciech Meyer
2012-05-28 15:52 ` Jeffrey Scofield
2012-05-27 18:19 ` Hongbo Zhang
2012-05-28 8:17 ` Paolo Donadeo
2012-05-30 12:41 ` Alain Frisch [this message]
2012-05-30 13:18 ` Markus Mottl
2012-05-30 13:37 ` Dan Bensen
2012-05-30 14:16 ` Hongbo Zhang
2012-05-30 14:23 ` Paolo Donadeo
[not found] ` <20120531081913.GA26742@securactive.lan>
2012-05-31 12:26 ` Paolo Donadeo
2012-05-31 12:38 ` Anil Madhavapeddy
2012-05-31 12:40 ` Anil Madhavapeddy
2012-05-31 12:46 ` Yaron Minsky
2012-05-31 12:47 ` Gabriel Scherer
2012-05-31 22:08 ` Paolo Donadeo
2012-05-30 14:14 ` Hongbo Zhang
2012-05-31 12:59 ` Alain Frisch
2012-05-31 13:21 ` Dmitry Grebeniuk
2012-05-31 14:30 ` Daniel Bünzli
2012-05-31 16:01 ` bob zhang
2012-05-31 17:28 ` Gerd Stolpmann
2012-05-31 18:03 ` Wojciech Meyer
2012-05-31 18:32 ` Gerd Stolpmann
2012-05-31 18:32 ` Hongbo Zhang
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=4FC61595.6070009@frisch.fr \
--to=alain@frisch.fr \
--cc=bobzhang1988@gmail.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