caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Markus Mottl <markus@mail4.ai.univie.ac.at>
To: Patrick M Doane <patrick@watson.org>
Cc: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>, caml-list@inria.fr
Subject: [Caml-list] Camlp4 and CamlIDL in main distribution?
Date: Wed, 5 Sep 2001 16:49:35 +0200	[thread overview]
Message-ID: <20010905164935.A22938@chopin.ai.univie.ac.at> (raw)
In-Reply-To: <Pine.BSF.3.96.1010905102235.66015A-100000@fledge.watson.org>; from patrick@watson.org on Wed, Sep 05, 2001 at 10:30:37 -0400

On Wed, 05 Sep 2001, Patrick M Doane wrote:
> Caml will be for the better when these two tools are merged.

I'd also say that having one distribution for OCaml and Camlp4 would
lead to fewer hassles for developers. Everytime I upgrade OCaml, I have
to upgrade Camlp4, too, because the byte code formats usually become
incompatible.

Nobody will feel hurt by the few extra bytes that Camlp4 adds to the
distribution, even if users don't need it.  The size of the distribution
is really not an argument anymore considering that most internet traffic
probably already consists of multi-megabyte MPEGs and videos, anyway.

CamlIDL could then also be added. I'd say that both of these tools are
so "standard" that they'd deserve a place in the main distribution.
Finally, I'd only have to issue one command then when I want to upgrade
to a new distribution... :-)

Regards,
Markus Mottl

-- 
Markus Mottl                                             markus@oefai.at
Austrian Research Institute
for Artificial Intelligence                  http://www.oefai.at/~markus
-------------------
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


      parent reply	other threads:[~2001-09-05 14:49 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-26 18:23 [Caml-list] Different types of streams Nicolas George
2001-08-27  9:49 ` Daniel de Rauglaudre
2001-08-27 17:47   ` Nicolas George
2001-08-28  8:20     ` Daniel de Rauglaudre
2001-08-28  9:33       ` Nicolas George
2001-08-29  8:39         ` Daniel de Rauglaudre
2001-09-05  1:03   ` Christian RINDERKNECHT
2001-09-05  7:34     ` Daniel de Rauglaudre
2001-09-05  8:02       ` STARYNKEVITCH Basile
2001-09-05  9:10         ` Daniel de Rauglaudre
2001-09-05  9:13         ` Alex Cowie
2001-09-05  9:30           ` Daniel de Rauglaudre
2001-09-05 10:58             ` Dave Mason
2001-09-05 12:06               ` Daniel de Rauglaudre
2001-09-05 12:56                 ` Dave Mason
2001-09-05 14:01                   ` Daniel de Rauglaudre
2001-09-05 13:29                 ` Nicolas George
2001-09-05 14:30                 ` Patrick M Doane
2001-09-05 14:44                   ` Daniel de Rauglaudre
2001-09-05 14:55                     ` Patrick M Doane
2001-09-05 19:39                     ` Brian Rogoff
2001-09-05 14:49                   ` Markus Mottl [this message]

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=20010905164935.A22938@chopin.ai.univie.ac.at \
    --to=markus@mail4.ai.univie.ac.at \
    --cc=caml-list@inria.fr \
    --cc=daniel.de_rauglaudre@inria.fr \
    --cc=patrick@watson.org \
    /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).