caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Threats on future of Camlp4
Date: Mon, 7 Oct 2002 10:52:38 +0200	[thread overview]
Message-ID: <20021007105238.B25685@verdot.inria.fr> (raw)
In-Reply-To: <20021007072153.GA1326@iliana>; from luther@dpt-info.u-strasbg.fr on Mon, Oct 07, 2002 at 09:21:53AM +0200

Hi,

On Mon, Oct 07, 2002 at 09:21:53AM +0200, Sven LUTHER wrote:

> Daniel, the one problem i have with separating camlp4 from ocaml, is
> that, if i remember well, the standalone camlp4 needed access to the
> ocaml sources to build.

No: Camlp4 is really an independant program. Yes it uses some files of
ocaml, but they are duplicated in the Camlp4 sources (directory
ocaml_stuff).

Between parentheses, these copied sources are the OCaml syntax tree,
which are not installed in the OCaml library. I had asked that they
are installed, like are installed some ".h" files, but it has been
refused. However, it would be useful, if people want to create another
preprocessor or use the OCaml syntax tree.

> If we separate again, what will be the situation on this same topic ?
> will you again depend on the ocaml source ? Is there not a cleaner
> solution for this ?

Programs often depend on versions of a compiler, for example with
the associated library.

> And also i am curious, what is so difficult with continuing to release
> camlp4 as part of ocaml, but have a separate CVS tree for developpment,
> that you sync with ocaml from time to time (and probably before each new
> release), in the same way as DRI for example maintains a separate
> development tree from XFree86 ?

I don't know the story of DRI and XFree86. The point is that I refuse
to sync: I consider that the ocaml team is not ready for the
industrialization level, although it pretends, because, at this level,
some "liberty of expression" should be more controlled. It is abnormal
that some member of the team considers that he is free to tell the
industrial contacts that the work of another member is "not serious".

Can you imagine what happens if the second of Microsoft tells to a
customer that Windows is "not serious"? The guy would be dismissed.

I shall return working inside the ocaml directory, if and only if the
ocaml team behave as professionnals.

Another example: I was very shocked, some time ago, that the icon of
Caml Light was "Joe Camel". Very funny, for students, but serious at
industialization level. When I said that, they laughed at me,
telling that I have no sense of humour.

Sorry, 6 millions deaths by cancer of lung EACH YEAR in the world does
not make me laugh. And the free ad of a seller of tobacco is serious
and important. I don't want to be a party to that. Industrials don't
have a "sense of humour", I am sorry. I am absolutely sure that we
have lost customers because of that. Even the name "Caml Light" is
absolutely suspect: students in France are learning it. And some of
them go here to make a thesis, or an a training course and bring their
packets of Camel, that they smoke, and smile at that. Perhaps they
think that we accept them better if they smoke Camels?

Therefore, the ocaml team is not professionnal, I am sorry.

-- 
Daniel de RAUGLAUDRE
daniel.de_rauglaudre@inria.fr
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:[~2002-10-07  8:52 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
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 [this message]
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=20021007105238.B25685@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;
as well as URLs for NNTP newsgroup(s).