From: Dave Mason <dmason@sarg.ryerson.ca>
To: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Threats on future of Camlp4
Date: Sun, 06 Oct 2002 16:28:43 -0400 [thread overview]
Message-ID: <200210062028.g96KShi14815@sarg.ryerson.ca> (raw)
In-Reply-To: Your message of "Sun, 06 Oct 2002 22:01:28 +0200." <20021006220127.B20005@verdot.inria.fr>
I agree 100% with Chris: Chill out guys!
>>>>> On Sun, 6 Oct 2002 22:01:28 +0200, Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr> said:
> Hi, On Sun, Oct 06, 2002 at 03:29:59PM -0400, Oleg wrote:
>> Could you explain what you mean by "compromising the future of
>> Camlp4"? I thought Camlp4 project was not affiliated with the
>> O'Caml project / team.
> It would be good, indeed, that Camlp4 be separated from OCaml, but
> the direction of the OCaml team refuses that energically. However it
> was a good compromise.
I think camlp4 is a very interesting system, but there are many cool
things in the world, and I don't have time to get deeply into all of
them. All I really care about is that there be some convenient way to
do parsers built into ocaml (i.e. without lex/yacc - and yes, there
are lots of times I'm willing to pay any resulting efficiency penalty).
I don't know who decided that camlp4 was the way to do that, but
somebody did, and so I hope that at least that much of camlp4 comes as
part of the ocaml distribution.
It may meet your (Daniel's) personal wishes that camlp4 be separated
from ocaml, but I think that for the rest of us, it is better that it
be shipped with ocaml.
Good luck and good wishes to all trying to clean up the personal mess.
../Dave
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-10-07 12:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 18:55 Daniel de Rauglaudre
2002-10-06 19:23 ` Chris Hecker
2002-10-06 19:52 ` Daniel de Rauglaudre
2002-10-06 21:01 ` brogoff
2002-10-06 21:09 ` Daniel de Rauglaudre
2002-10-06 19:29 ` Oleg
2002-10-06 20:01 ` Daniel de Rauglaudre
2002-10-06 20:24 ` Alessandro Baretta
2002-10-06 20:24 ` Daniel de Rauglaudre
[not found] ` <200210062143.g96Lhix15834@orchestra.cs.caltech.edu>
2002-10-07 2:47 ` Daniel de Rauglaudre
2002-10-06 20:28 ` Dave Mason [this message]
2002-10-06 20:50 ` Daniel de Rauglaudre
2002-10-06 20:45 ` Oleg
2002-10-06 21:03 ` Daniel de Rauglaudre
2002-10-06 21:46 ` Florian Douetteau
2002-10-07 2:56 ` Daniel de Rauglaudre
2002-10-06 23:54 ` Markus Mottl
2002-10-07 9:06 ` Daniel de Rauglaudre
2002-10-11 11:34 ` Kontra, Gergely
2002-10-11 12:56 ` Alessandro Baretta
2002-10-11 13:15 ` [Caml-list] Future " Daniel de Rauglaudre
2002-10-12 21:45 ` Oleg
2002-10-13 9:02 ` Daniel de Rauglaudre
2002-10-11 16:36 ` [Caml-list] Syntax brogoff
2002-10-07 7:21 ` [Caml-list] Threats on future of Camlp4 Sven LUTHER
2002-10-07 8:52 ` Daniel de Rauglaudre
2002-10-07 11:25 ` Sven LUTHER
2002-10-07 11:30 ` Daniel de Rauglaudre
2002-10-07 11:55 ` Sven LUTHER
2002-10-08 7:57 ` Alessandro Baretta
[not found] ` <nhalm59cf0s.fsf@malabar.mitre.org>
2002-10-08 14:05 ` Alessandro Baretta
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=200210062028.g96KShi14815@sarg.ryerson.ca \
--to=dmason@sarg.ryerson.ca \
--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