From: Jon Harrop <jonathandeanharrop@googlemail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Metaprogramming features
Date: Sat, 4 Oct 2008 15:31:18 +0100 [thread overview]
Message-ID: <200810041531.18370.jon@ffconsultancy.com> (raw)
In-Reply-To: <20081004082346.GA18277@annexia.org>
On Saturday 04 October 2008 09:23:46 Richard Jones wrote:
> On Sat, Oct 04, 2008 at 03:03:04AM +0100, Jon Harrop wrote:
> > On Saturday 04 October 2008 01:49:08 Stefano Zacchiroli wrote:
> > > Sorry if I'm being too frank, but I don't see the usefulness of your
> > > post. I would love to see basic meta-programming feature in vanilla
> > > Caml, but the way to make it happen is for sure not lobbying / making
> > > noise. The way is provide patches which implement the requested
> > > feature.
> >
> > If try..finally will not be accepted what makes you think that a
> > MetaOCaml patch would be accepted?
>
> Where did you post the working compiler patch that implements
> try/finally?
I asked if it would be worth doing so before I even attempted it and was told
that it would not be worth attempting by Pierre Weis. Xavier Leroy told me
that copyright issues in French law essentially prohibit contributions from
non-French programmers.
> Where did you nurse the patch through many iterations,
> as the language designers asked you to fix one thing and another,
> before the final patch was rejected?
I would like to think that the OCaml community has try..finally pinned down
now. It is the first example on every Camlp4 tutorial after all...
I'm not saying that there is anything wrong with having a language
implementation written by language researchers for language research but
almost all users would benefit enormously from a variety of simple
improvements that the community could easily implement themselves were it
feasible to get changes absorbed upstream more quickly. Now that OCaml is
gaining traction in industry there are also a growing number of people
willing to throw money around to get improvements made and we could all be
benefitting from that.
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
next prev parent reply other threads:[~2008-10-04 13:30 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
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 [this message]
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=200810041531.18370.jon@ffconsultancy.com \
--to=jonathandeanharrop@googlemail.com \
--cc=caml-list@yquem.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