caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alessandro Baretta <alex@baretta.com>
To: Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Unix.file_descr -> int ???
Date: Wed, 19 Jun 2002 00:41:38 +0200	[thread overview]
Message-ID: <3D0FB722.6000009@baretta.com> (raw)
In-Reply-To: <000101c21705$d9f23640$0501a8c0@lexifi01>



Jean-Marc Eber wrote:
> happy that you posted it on the list.
> I didn't want to propose it to you, because I thank you wanted it to
> stay non public.
> JM


Oh, it was definitely meant to be public. It was astonishing 
for me to hear an ex-IBM researcher, a man on science, one 
would imagine, say that his customers are not interested in 
any new or advanced stuff. And I'm pretty sure he knows what 
he's talking about.

How can customers not realize that improvements in the 
production technology necessarily translate to reduced costs 
and improved quality? I'd be willing to pay more for a piece 
of software, if I had a compiler-generated proof that no 
segmentation fault can occur. There is a dose of absurdity 
in all this--although there is some sense, as well.

Xavier, let me ask a dumb question, if you don't mind: how 
do you choose which processor architectures to port ocamlopt 
to? Could .NET simply be regarded as a new "architecture" 
for ocamlopt?

At any rate, I am writing and deploying O'Caml programs. My 
customer has no internal EDP resources, so they are relying 
entirely on me. Of course, they did not ask what language I 
would write the code in. They only care to see it work, and 
they are not disappointed. Long live the Caml!

Alex

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


  parent reply	other threads:[~2002-06-18 22:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-18 13:38 Alessandro Baretta
     [not found] ` <000101c21705$d9f23640$0501a8c0@lexifi01>
2002-06-18 22:41   ` Alessandro Baretta [this message]
2002-06-19 16:22     ` John Max Skaller
2002-06-20 11:23     ` Xavier Leroy
2002-06-20 11:52       ` Markus Mottl
2002-06-20 13:14       ` Alessandro Baretta
2002-06-20 13:23         ` Stefano Lanzavecchia
2002-06-20 16:22           ` Alessandro Baretta
2002-06-20 14:42         ` YAMAGATA yoriyuki
2002-06-21 16:16           ` [Caml-list] proposal for library Christophe Raffalli
2002-06-22 11:56             ` Nicolas Cannasse
  -- strict thread matches above, loose matches on Subject: below --
2002-06-20 12:24 [Caml-list] Unix.file_descr -> int ??? Ohad Rodeh
2002-06-12  9:53 Damien Doligez
2002-06-12  9:57 ` Jacques Garrigue
2002-06-12 11:04   ` Jacques Garrigue
2002-06-11 14:31 Max Kirillov
2002-06-11 15:40 ` Bruno.Verlyck
2002-06-11 15:45 ` Xavier Leroy
2002-06-11 19:26   ` Max Kirillov
2002-06-11 23:12     ` Berke Durak
2002-06-12  0:10     ` Jacques Garrigue
2002-06-12  8:08     ` Xavier Leroy
2002-06-12  7:42   ` Basile STARYNKEVITCH
2002-06-12  8:21     ` Xavier Leroy
2002-06-12 16:06       ` Max Kirillov
2002-06-13 10:24       ` Jean-Marc Eber
2002-06-12 13:09     ` Bruno.Verlyck
2002-06-12 15:44   ` John Max Skaller

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=3D0FB722.6000009@baretta.com \
    --to=alex@baretta.com \
    --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).