caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Patrick M Doane <patrick@watson.org>
To: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Different types of streams
Date: Wed, 5 Sep 2001 10:30:37 -0400 (EDT)	[thread overview]
Message-ID: <Pine.BSF.3.96.1010905102235.66015A-100000@fledge.watson.org> (raw)
In-Reply-To: <20010905140610.V5393@verdot.inria.fr>

On Wed, 5 Sep 2001, Daniel de Rauglaudre wrote:

> > I don't think anyone is arguing against fixing the implementation
> 
> Camlp4 fixes the implementation. It is complicated to add the same
> code in OCaml because it is about manipulatation of pieces of program,
> which is very easy and simple in Camlp4 and very complicated with
> OCaml. If you are not happy, implement the optimization yourself in
> OCaml. Good luck.

What is wrong with:

  - Including camlp4 in the standard caml distribution
  - Modifiying the caml compilers to always use camlp4 for preprocessing.

To the user, this fixes the implementation without any modification to
how they use their tools. 

BTW, it has been my impression that the Caml team is not too interested in
external development, so implementing the optimization without camlp4 is
not much of an option.

> The point is *not* to remove streams!!!! Streams and their LL1 parsers
> remain!!! I just ask people to preprocess by "-pp camlp4o". Is that
> so complicated? Are you allergic to my program?

I'm not allergic to your program, but other people may be.  Until camlp4
is part of the caml distribution, the proposal is still to remove streams. 
For developers who distribute source code, we now have to demand that
another package be installed on the user's system.  Caml will be for the
better when these two tools are merged.

Patrick Doane

-------------------
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:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-26 18:23 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 [this message]
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                   ` [Caml-list] Camlp4 and CamlIDL in main distribution? Markus Mottl

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=Pine.BSF.3.96.1010905102235.66015A-100000@fledge.watson.org \
    --to=patrick@watson.org \
    --cc=caml-list@inria.fr \
    --cc=daniel.de_rauglaudre@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;
as well as URLs for NNTP newsgroup(s).