From: Fabrice Le Fessant <fabrice.le_fessant@inria.fr>
To: Hendrik Tews <tews@tcs.inf.tu-dresden.de>
Cc: jeanmarc.eber@lexifi.com
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Whither the Caml Consortium?
Date: Tue, 30 Oct 2001 10:21:02 +0100 (CET) [thread overview]
Message-ID: <15326.28926.702172.267468@lachesis.inria.fr> (raw)
In-Reply-To: <15326.27209.775213.987022@gargle.gargle.HOWL>
> Indeed I was not aware of this. Where are these patches
> documented? I only found cdk/sources/ocaml.patches/README, which
> describes only 2 of the 17 patches.
Most of the patches in the CDK are useful to improve the compilation
and distribution of the CDK (eg binary distribs independent of linux
distributions), and are not useful for other ocaml users. However,
some patches discussed on the mailing-list have been integrated and
can be used by users. For example:
14_yacc.patch is Thierry Bravier's ocamlyacc patch, to allow symbolic $
variables in mly files.
13_scaml.patch is described on http://algol.prosalg.no/~malc/scaml .
16_clink.patch is used to allow recursive modules in very simple
cases (forward declaration of functions).
17_option.patch is a patch to allow optional values in modules
(from Alain Frisch).
As said by Xavier, these patches are not included in the standard
distribution for good reasons (either they need to be improved, or
better tested, or a better general solution is coming). They are
mainly in the CDK for beta-testing, and they will be kept until either
a big bug appears or a better replacement is found.
- 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-10-30 9:20 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-15 20:37 Brian Rogoff
2001-10-15 20:55 ` Patrick M Doane
2001-10-19 23:23 ` Michel Mauny
2001-10-20 2:50 ` Brian Rogoff
2001-10-20 3:58 ` Julian Assange
2001-10-20 15:29 ` Markus Mottl
2001-10-21 1:17 ` Brian Rogoff
2001-10-21 23:06 ` Markus Mottl
2001-10-22 15:47 ` Rolf Wester
2001-10-23 10:22 ` Markus Mottl
2001-10-23 13:41 ` Rolf Wester
2001-10-24 13:52 ` Mattias Waldau
2001-10-24 14:11 ` Markus Mottl
2001-10-24 14:18 ` Cuihtlauac ALVARADO
2001-10-25 6:05 ` Sven
2001-10-26 14:16 ` Dmitry Bely
2001-10-26 15:51 ` Francois Rouaix
2001-10-26 8:45 ` Benjamin C. Pierce
2001-10-24 13:59 ` Markus Mottl
2001-10-25 9:54 ` Frank Atanassow
2001-10-24 13:56 ` Mike Leary
2001-10-22 17:25 ` Michel Mauny
2001-10-22 17:36 ` Ken Rose
2001-10-22 19:08 ` Markus Mottl
2001-10-23 10:08 ` Daniel de Rauglaudre
2001-10-23 10:52 ` Markus Mottl
2001-10-24 14:48 ` Xavier Leroy
2001-10-24 15:17 ` Markus Mottl
2001-10-24 17:35 ` Joshua D. Guttman
2001-10-25 18:46 ` Michel Mauny
2001-10-24 15:57 ` Sven
2001-10-24 17:05 ` georges mariano
2001-10-25 6:13 ` Sven
2001-10-25 17:36 ` Michel Mauny
2001-10-25 10:00 ` Hendrik Tews
2001-10-25 15:45 ` Fabrice Le Fessant
2001-10-30 8:52 ` Hendrik Tews
2001-10-30 9:21 ` Fabrice Le Fessant [this message]
2001-10-25 18:37 ` Michel Mauny
2001-10-26 9:56 ` Sven
2001-10-30 9:00 ` Hendrik Tews
2001-10-26 12:13 ` [Caml-list] user contributions to the core OCaml distribution? Xavier Leroy
2001-10-29 11:15 ` Sven
2001-10-22 18:41 ` [Caml-list] Whither the Caml Consortium? Markus Mottl
2001-10-22 18:47 ` 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=15326.28926.702172.267468@lachesis.inria.fr \
--to=fabrice.le_fessant@inria.fr \
--cc=jeanmarc.eber@lexifi.com \
--cc=tews@tcs.inf.tu-dresden.de \
/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).