From: Fabrice Le Fessant <fabrice.le_fessant@inria.fr>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] compiler patches in the CDK
Date: Tue, 6 Nov 2001 14:49:30 +0100 (CET) [thread overview]
Message-ID: <15335.60010.473147.961881@lachesis.inria.fr> (raw)
In-Reply-To: <20011106152001.C3221@pauillac.inria.fr>
Xavier wrote:
> This is one thing I'm not sure to understand about the CDK.
>
> My initial view of the CDK is as a pre-packaged binary installation of
> OCaml plus lots of user-contributed libraries and tools: a very
> convenient thing indeed for users who want an OCaml development
> environment that works and that is rich enough, without the hassle of
> tracking down and installing all the bits themselves. Excellent idea.
>
> But then we learn that the CDK also includes some experimental, not
> much tested patches to the OCaml compilers, and that by doing this
> Fabrice intends the CDK to serve also as a beta-test for these
> experimental extensions and changes.
>
> So, is the CDK a stable, convenient distribution for users who
> want something that works with no hassle, or an experimental
> distribution for users who want to sit on the bleeding edge and
> beta-test things?
I understand that the idea of untested patches being included in the
CDK can frighten users. Two replies:
1) Most patches which were included in the CDK until a recent date
were very simple patches, which only modify small well delimited
parts of the compiler. Bugs in these patches are very
unlikely. However, it is true that I've added some experimental
patches very recently, with the idea that the CDK should also
welcome contributed patches to the compiler as it welcomes
contributed libraries, some of these patches being often asked for
on the caml mailing-list. I've tried to read these patches
carefully, before including them, to reduce the risk of
introducing bugs. In particular, most of them require the use of
special keywords or options to trigger them, and so, should not
introduce bugs for users that don't use them.
2) As a result of your mail, and of the discussion of this morning, I
will remove all experimental patches from the compiler distributed
in the CDK. However, since I think some of the experimental
patches can still be useful for some users, I will investigate if
I can add a second compiler, something like ocamlc-patched and
ocamlopt-patched, that will contain some of the patches and still
be compatible with object files generated by ocamlc and ocamlopt.
Hope this answers your curiosity.
- Fabrice
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-11-06 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 3:08 [Caml-list] native code optimization priorities Chris Hecker
2001-10-31 7:50 ` Fabrice Le Fessant
2001-11-06 14:20 ` [Caml-list] compiler patches in the CDK Xavier Leroy
2001-11-06 13:49 ` Fabrice Le Fessant [this message]
2001-11-06 14:06 ` [Caml-list] native code optimization priorities Xavier Leroy
[not found] ` <20011106154533.D27723@chopin.ai.univie.ac.at>
2001-11-08 9:45 ` Xavier Leroy
[not found] ` <Pine.SOL.4.20.0111061141330.10389-100000@godzilla.ics.uci.edu>
2001-11-08 9:59 ` Xavier Leroy
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=15335.60010.473147.961881@lachesis.inria.fr \
--to=fabrice.le_fessant@inria.fr \
--cc=caml-list@pauillac.inria.fr \
--cc=xavier.leroy@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