From: Georges Mariano <georges.mariano@inrets.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Future of Camlp4
Date: Thu, 6 Feb 2003 17:10:09 +0100 [thread overview]
Message-ID: <20030206171009.4dd1afca.georges.mariano@inrets.fr> (raw)
In-Reply-To: <20030206152053.A32089@pauillac.inria.fr>
On Thu, 6 Feb 2003 15:20:53 +0100
Xavier Leroy <xavier.leroy@inria.fr> wrote:
> developers, as well as those users that voiced their opinions on this
> mailing list, were not favorable to this split, as it appeared (to
> them) to be a step backwards.
Well, I think that choosing the way where ddr will stop working on
camlp4 (thus keeping camlp4 in its current state instead of allowing it
to progress [which is the real interest in the field of software
enginnering research]) is also a step backwards.
I don't think that it is a too huge price to pay if the "freedom" of ddr
is the price of the camlp4's progress... In those days, I have to manage
approximatively more than 600 pieces of software to keep my computer
doing what I want
> Hope this clears up the uncertainty and doubts.
Well, not really but it doesn't really matter since I'm suspecting that
we are not totally informed (from both "sources" ;-) about all aspects
of the «crisis»...
(sorry) I can't remember if the following way has been exposed on this
list :
Can we imagine a kind of camlp4 fork ? That is, ddr freely working on
its own "camlp4+" and the OCaml maintaining the "current" camlp4 inside
the distribution ?
Daniel, what do you think about this ??
Cheers
--
mailto:georges.mariano@inrets.fr tel: (33) 03 20 43 84 06
INRETS, 20 rue Élisée Reclus fax: (33) 03 20 43 83 59
BP 317 -- 59666 Villeneuve d'Ascq
http://www3.inrets.fr/estas/mariano
-------------------
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:[~2003-02-06 16:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-06 12:28 Daniel de Rauglaudre
2003-02-06 12:55 ` Jérôme Marant
2003-02-06 13:01 ` Sven Luther
2003-02-06 13:23 ` Daniel de Rauglaudre
2003-02-06 13:59 ` Mattias Waldau
2003-02-06 14:20 ` Xavier Leroy
2003-02-06 15:59 ` Sven Luther
2003-02-06 16:30 ` Xavier Leroy
2003-02-06 16:10 ` Georges Mariano [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-06 23:54 [Caml-list] Threats on future " Markus Mottl
2002-10-11 11:34 ` Kontra, Gergely
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-04 15:14 [Caml-list] Pattern matching and strings Luc Maranget
2002-10-04 19:38 ` Alessandro Baretta
2002-10-05 6:34 ` [Caml-list] Camlp4 (Was: Pattern matching and strings) Daniel de Rauglaudre
2002-10-05 12:47 ` Sven LUTHER
2002-10-05 12:42 ` Daniel de Rauglaudre
2002-10-05 13:41 ` Michel Mauny
2002-10-05 13:47 ` Daniel de Rauglaudre
2002-10-05 14:09 ` Michel Mauny
2002-10-05 18:13 ` Alessandro Baretta
2002-10-05 20:30 ` [Caml-list] Future of Camlp4 Daniel de Rauglaudre
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=20030206171009.4dd1afca.georges.mariano@inrets.fr \
--to=georges.mariano@inrets.fr \
--cc=caml-list@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