Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Brian Rogoff <bpr@best.com>
To: OCAML <caml-list@inria.fr>
Subject: Re: convincing management to switch to Ocaml
Date: Mon, 30 Aug 1999 22:50:30 -0700 (PDT)	[thread overview]
Message-ID: <Pine.BSF.4.10.9908302234040.5930-100000@shell5.ba.best.com> (raw)
In-Reply-To: <3.0.6.32.19990828162457.009677a0@mail.triode.net.au>

On Sat, 28 Aug 1999, John Skaller wrote:
> At 12:00 27/08/99 +0200, Andreas Rossberg wrote:
> >You are right that there are more than just technical reasons for
> >choosing a particular technology. And many (not all) of these arguments
> >have their justification. However, I don't agree that in the particular
> >case of OCaml vs. C++ there exist any _technical_ advantages in the
> >language C++ itself.
> 
> 	I am not sure due to inexperience with Ocaml, but I would
> guess (since I know C++ backwards) that the main issue would
> be performance, and a secondary issue the ocaml compilation
> system (with the requirement on a strict ordering which is
> getting in my way at present).

Consider that C is roughly a subset of C++. Since OCaml is technically
superior in every way to C, the OCaml implementors are then not very smart 
since certain libraries (bignums, regexps, ...) are coded in C, not pure 
OCaml, even though they could easily be written in pure OCaml. Since we
know the OCaml implementors are very smart, we have reduced the
hypothesis of unqualified OCaml superiority to an absurdity :-).

Use the right tool for the job. I probably wouldn't write hardware
simulation models in OCaml. I probably wouldn't write the program to 
do clock tree insertion or scan insertion (essentially build a parse tree 
of structural Verilog and then abuse it) in anything else. Well, maybe 
SML or Icon would not be horrible...

-- Brian





  parent reply	other threads:[~1999-08-31 17:14 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 [this message]
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
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=Pine.BSF.4.10.9908302234040.5930-100000@shell5.ba.best.com \
    --to=bpr@best.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