From: Markus Mottl <markus@oefai.at>
To: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Threats on future of Camlp4
Date: Mon, 7 Oct 2002 01:54:50 +0200 [thread overview]
Message-ID: <20021006235450.GB5700@kiefer.ai.univie.ac.at> (raw)
In-Reply-To: <20021006220127.B20005@verdot.inria.fr>
On Sun, 06 Oct 2002, Daniel de Rauglaudre wrote:
> On Sun, Oct 06, 2002 at 03:29:59PM -0400, Oleg wrote:
> 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 want to make my contribution to this flamewar short:
* Camlp4 is useful.
* Camlp4 should be part of the main distribution, because a not
insignificant number of people uses it, be it for streams or
different syntax.
* Development and stable versions are absolutely common in software
development. I don't see any reason why there shouldn't be
corresponding branches in the CVS, which keeps good track of the
differences. No need to separate Camlp4 from the rest of the project:
just agree on release dates and that's it.
* Concerning the point that somebody says "X is a waste of time". My
PhD-supervisor thinks that OCaml is a waste of time. So what? I
don't like Prolog...
Otherwise, please resolve personal issues over a beer in a bar or in a
fight outside, whichever you prefer. As long as all of you stay healthy
for further development, OCaml-users will be happy... ;-)
Regards,
Markus Mottl
--
Markus Mottl markus@oefai.at
Austrian Research Institute
for Artificial Intelligence http://www.oefai.at/~markus
-------------------
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-06 23:54 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
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 [this message]
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=20021006235450.GB5700@kiefer.ai.univie.ac.at \
--to=markus@oefai.at \
--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