From: Francois Rouaix <frouaix@liquidmarket.com>
To: STARYNKEVITCH Basile <Basile.Starynkevitch@cea.fr>
Cc: caml-list@inria.fr
Subject: Re: convincing management to switch to Ocaml
Date: Fri, 30 Jul 1999 14:30:05 -0700 [thread overview]
Message-ID: <199907302130.OAA05661@fiji01.liquidmarket.com> (raw)
In-Reply-To: Your message of "Wed, 28 Jul 1999 16:47:34 +0200." <14239.6150.864319.797849@gargle.gargle.HOWL>
> Does any one have clues or positive experience about convincing
> management to switch to Ocaml?
> My manager's arguments are:
>
> * There is an existing (important) code base (a static C code
> analyser) coded in C and C++ and it is unreasonable to recode it.
Interface OCaml to the C code (C++ is harder if you use exception)
if that makes sense (but maybe it doesn't).
> * Ocaml is a slow implentation
Can be refuted. ocamlopt is not that bad, and brings more
advantages (e.g. symbolic-manipulation requires decent and safe memory
allocation, safe typing and all that).
> * Ocaml is hard to learn for people (fluent in C++) with less than a PhD
> in computer science (unfortunately for me, I do hold a PhD in
> Artif. Intel.)
Simple test: throw the OCaml distribution at a C++ engineer, ask the guy
to write a semi-simple program in it. Chances are the engineer will be able
to do that in one afternoon (including installing the compiler).
This is based on a true story (tech due diligence on us by people we're working
with, I can't disclose the name).
> * Ocaml might not last long (but ESPRIT projects don't last neither)
True, but the compiler is stable. How often do you need to update the compiler
?
> ESPRIT projects are supposed to be preindustrial and OCaml is only academic
How many ESPRIT projects actually produce code that is being used ?
--f
next prev parent reply other threads:[~1999-08-12 9:58 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-28 14:47 STARYNKEVITCH Basile
1999-07-30 9:00 ` Markus Mottl
1999-08-13 10:32 ` John Skaller
1999-08-25 1:51 ` Frank A. Christoph
1999-08-25 3:50 ` John Skaller
1999-08-25 6:34 ` Frank A. Christoph
1999-08-26 18:36 ` Stefan Monnier
1999-08-29 6:08 ` John Skaller
1999-08-27 10:00 ` Andreas Rossberg
1999-08-28 6:24 ` John Skaller
1999-08-30 15:59 ` Sylvain BOULM'E
1999-08-31 5:50 ` Brian Rogoff
1999-08-28 19:51 ` Dave Mason
1999-08-30 19:05 ` Xavier Leroy
1999-08-30 8:02 ` Pierre Weis
1999-08-30 19:35 ` John Skaller
1999-08-31 17:10 ` Pierre Weis
1999-09-03 6:56 ` John Skaller
1999-08-31 19:03 ` Stefan Monnier
1999-09-03 7:28 ` John Skaller
1999-08-31 0:13 ` John Prevost
1999-08-31 5:19 ` John Skaller
1999-08-31 6:35 ` John Prevost
1999-09-03 5:42 ` John Skaller
1999-08-31 16:24 ` Gerard Huet
1999-07-30 14:42 ` John Skaller
1999-07-30 18:49 ` Gerd Stolpmann
1999-07-30 21:30 ` Francois Rouaix [this message]
1999-08-12 10:36 ` Reply to: " Jens Olsson
1999-08-16 18:33 ` Chris Tilt
1999-08-12 12:15 ` Frank A. Christoph
1999-08-15 8:14 ` Friedman Roy
-- strict thread matches above, loose matches on Subject: below --
1999-09-07 7:24 TommyHallgren
[not found] <John Skaller's message of "Tue, 31 Aug 1999 15:19:48 +1000">
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=199907302130.OAA05661@fiji01.liquidmarket.com \
--to=frouaix@liquidmarket.com \
--cc=Basile.Starynkevitch@cea.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