caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Future of Camlp4
Date: Thu, 6 Feb 2003 16:59:36 +0100	[thread overview]
Message-ID: <20030206155936.GA6428@iliana> (raw)
In-Reply-To: <20030206152053.A32089@pauillac.inria.fr>

On Thu, Feb 06, 2003 at 03:20:53PM +0100, Xavier Leroy wrote:
> Camlp4 remains part of the OCaml distribution, and will be maintained
> like everything else.  Yes, it will probably not evolve as quickly as
> if Daniel was still working on it.  and Daniel's programming talents
> will be missed.  However, all the features of the current Camlp4 (that
> from release 3.06 of OCaml) will still be available and properly
> maintained in the future releases of OCaml.

Is it not possible to have it both way ? Have camlp4 stay in ocaml as
usual, and have a second camlp4 which could be used as a drop-in
replacement, which Daniel could make evolve more accordying to his
wishes, and were parts can be folded back into the ocaml camlp4 version
as they mature, prove themselves, whatever. This would met both yours
and Daniel's wish, and also be a good thing for the users who could
choose between both version for their own code. This kind of dual
developpment track has already shown it works for other project, as for
example the XFree86/DRI dual developpment trees, and there is no reason
it would not work for ocaml also. Sure it would mean a bit of
fragmentation, but i guess most code that needs to get shared does not
use camlp4 anyway, or at least could be coded in a compatible way.

Friendly,

Sven Luther
-------------------
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


  reply	other threads:[~2003-02-06 15:59 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 [this message]
2003-02-06 16:30     ` Xavier Leroy
2003-02-06 16:10   ` Georges Mariano
  -- 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=20030206155936.GA6428@iliana \
    --to=luther@dpt-info.u-strasbg.fr \
    --cc=caml-list@inria.fr \
    --cc=xavier.leroy@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).