caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Hongbo Zhang <bobzhang1988@gmail.com>
To: Dan Bensen <danbensen@att.net>
Cc: Alain Frisch <alain@frisch.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] Re: Syntax extensions without Camlp4
Date: Wed, 30 May 2012 10:16:42 -0400	[thread overview]
Message-ID: <4FC62BCA.4030108@gmail.com> (raw)
In-Reply-To: <1338385022.96299.YahooMailRC@web180009.mail.gq1.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 960 bytes --]

On 5/30/12 9:37 AM, Dan Bensen wrote:
>
> > > I don't think it's good to downplay camlp4.
> > > we need more documentation and more tests.
>
> > (The new) Camlp4 has been here for several years.
> > Documentation and tests are still lagging behind.
>
> Is it possible for Inria or someone else to provide
> funding for that?  I would like to help out starting
> sometime in the summer.
>
Actually I am writing a book about the internal part of camlp4 (100~200 
pages),
but nobody seems to care about it.
> > the most common uses of camlp4 might be based on a much
> > simpler approach ... Coq is one of the few examples of
> > a big project that relies on other aspects of camlp4
>
> Why not focus on optimizing new lightweight tools for
> small problems and keep camlp4 for big ones?  It wouldn't
> be so bad if it were documented better.
I think it's a good idea to build simple tools on top of existing more 
powerful tools instead of dropping the latter.


[-- Attachment #2: Type: text/html, Size: 1949 bytes --]

  reply	other threads:[~2012-05-30 14:17 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
2012-05-30 13:18     ` Markus Mottl
2012-05-30 13:37     ` Dan Bensen
2012-05-30 14:16       ` Hongbo Zhang [this message]
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=4FC62BCA.4030108@gmail.com \
    --to=bobzhang1988@gmail.com \
    --cc=alain@frisch.fr \
    --cc=caml-list@inria.fr \
    --cc=danbensen@att.net \
    /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).