From: "Yaron Minsky" <yminsky@gmail.com>
To: "Jon Harrop" <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] [OSR] OCaml Standard Recommandation Process
Date: Sun, 27 Jan 2008 16:47:47 -0500 [thread overview]
Message-ID: <891bd3390801271347y56af21cam492ccaac1348bb05@mail.gmail.com> (raw)
In-Reply-To: <200801272107.23900.jon@ffconsultancy.com>
[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]
On Jan 27, 2008 4:07 PM, Jon Harrop <jon@ffconsultancy.com> wrote:
> On Sunday 27 January 2008 19:07:01 David Teller wrote:
> > You are correct, I should have been more specific. The idea is to
> > discuss
> > * libraries
> > * Camlp4 extensions
> > * language features that may be implemented as a combination of
> > libraires and Camlp4 extensions
> > * actual code.
>
> Would it not be much easier and much more productive to simply fork the
> OCaml
> distribution and address these issues at source? You could then address
> many
> other issues like improving the stdlib, adding a "try..finally" construct
> to
> the language, adding features to help with the brittle binding problem and
> opening the compiler's internal representations to the outside world.
That seems like a fairly awful idea to me. Trying to develop the core
language away from the confines of INRIA seems expensive and unlikely to go
well. The INRIA team understands the core of the language like no one else,
after all, and it will be hard to replace that expertise.
I do think there is value in outside companies thinking carefully about a
limited set of improvements that (a) can only be fixed in the core language
and (b) would make it easier for outsiders to add necessary features.
One role I would like to see the caml team take upon itself is that of
blessing standardization efforts. If INRIA had a link on its site to a
recommended batteries-included distribution, that would help the community
coalesce around that distribution. Obviously trying to choose winners in
this way is tricky and not to be done lightly, but I do think there's a good
chance that it will become important.
y
[-- Attachment #2: Type: text/html, Size: 2070 bytes --]
next prev parent reply other threads:[~2008-01-27 21:48 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 13:23 David Teller
2008-01-27 13:52 ` [Caml-list] " Paolo Donadeo
2008-01-27 14:24 ` Yaron Minsky
2008-01-27 19:07 ` David Teller
2008-01-27 21:07 ` Jon Harrop
2008-01-27 21:47 ` Yaron Minsky [this message]
2008-01-28 11:06 ` David Teller
2008-01-28 12:04 ` Jon Harrop
2008-01-28 12:31 ` David Teller
2008-01-28 14:23 ` Brian Hurt
2008-01-28 15:15 ` Loup Vaillant
2008-01-28 15:40 ` Brian Hurt
2008-01-28 19:46 ` Jon Harrop
2008-01-28 15:25 ` Jon Harrop
2008-01-28 16:06 ` Christophe TROESTLER
2008-01-28 16:20 ` Nicolas Pouillard
2008-01-28 16:45 ` Christophe TROESTLER
2008-01-28 16:51 ` Olivier Andrieu
2008-01-28 19:58 ` Jon Harrop
2008-01-29 7:51 ` Gordon Henriksen
2008-01-28 20:49 ` Jon Harrop
2008-01-28 22:05 ` Till Varoquaux
2008-01-28 23:10 ` Jon Harrop
2008-01-28 16:37 ` Brian Hurt
2008-01-28 17:30 ` David Teller
2008-01-28 20:43 ` Jon Harrop
2008-01-28 21:12 ` Gerd Stolpmann
2008-01-28 21:39 ` Jon Harrop
2008-01-29 16:49 ` Edgar Friendly
2008-01-30 8:52 ` Sylvain Le Gall
2008-01-30 10:02 ` [Caml-list] " Jon Harrop
2008-01-30 12:12 ` Vincent Hanquez
2008-01-28 21:43 ` [Caml-list] " Dario Teixeira
2008-01-29 7:59 ` Francois Pottier
2008-01-28 22:07 ` Arnaud Spiwack
2008-01-27 14:36 ` Michaël Grünewald
2008-01-27 15:10 ` Dario Teixeira
2008-01-28 13:38 ` Sylvain Le Gall
2008-01-28 13:52 ` [Caml-list] " David Teller
2008-01-28 0:23 ` [Caml-list] " Oliver Bandel
2008-01-30 9:43 ` Sylvain Le Gall
2008-01-30 20:25 ` [Caml-list] " blue storm
2008-01-30 20:49 ` Sylvain Le Gall
2008-01-30 20:54 ` [Caml-list] " Eric Cooper
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=891bd3390801271347y56af21cam492ccaac1348bb05@mail.gmail.com \
--to=yminsky@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.com \
/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