Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Future of Camlp4
Date: Thu, 6 Feb 2003 14:23:25 +0100	[thread overview]
Message-ID: <20030206142325.A24055@verdot.inria.fr> (raw)
In-Reply-To: <20030206130116.GA5350@iliana>; from luther@dpt-info.u-strasbg.fr on Thu, Feb 06, 2003 at 02:01:16PM +0100

Hi,

On Thu, Feb 06, 2003 at 02:01:16PM +0100, Sven Luther wrote:

> Mmm, if i am not wrong, camlp4 was developped separatedly, but had a
> dependency on the ocaml source to build. I don't personally use camlp4,
> but i feel that build depending on the ocaml sources is a nightmare for
> package maintainers like me.

I don't say that there is no drawback (with "nightmare", you exaggerate).
Just consider the drawbacks of the different solutions.

> Anyway, would you care to give a bit more details about the practical
> results of the separation ? What about the streams ?

The streams could be put back in the OCaml distribution as they were
before. If the separation is accepted, I can put them in the OCaml
archive with, better, some small code to avoid the problem of missing
of tail recursion which was there before.

> Is it really not possible to resolv your political differences (with
> political, i guess you mean caml politics, not the other ones :)).

Human reasons are political reasons. I am not a machine to produce
code and what I ask is not too much. As the creator of Camlp4, I
have the right to speak about my conditions of work and the right
to say how my work have to be distributed. If you ignore it, it
is normal that I stop working.

-- 
Daniel de RAUGLAUDRE
http://cristal.inria.fr/~ddr/

-------------------
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 16:38 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 [this message]
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
  -- 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=20030206142325.A24055@verdot.inria.fr \
    --to=daniel.de_rauglaudre@inria.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