From: Ville-Pertti Keinonen <will@exomi.com>
To: Nicolas FRANCOIS (AKA El Bofo) <nicolas.francois@free.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Great Programming Language Shootout Revived
Date: Sat, 19 Jun 2004 14:18:44 +0300 [thread overview]
Message-ID: <6D5202BA-C1E2-11D8-B4A4-000393863F70@exomi.com> (raw)
In-Reply-To: <20040619022648.7864665d.nicolas.francois@free.fr>
On Jun 19, 2004, at 3:26 AM, Nicolas FRANCOIS (AKA El Bofo) wrote:
> Le Fri, 18 Jun 2004 10:56:38 +0300 Ville-Pertti Keinonen
> <will@exomi.com>
> a écrit :
>> I looked at it a bit earlier (when it was posted on LtU), and MLton
>> and
>> SML/NJ were both ahead of OCaml in the overall scorecard for CPU.
>> There was probably a bug in computing the totals, as the raw scores
>> don't seem to have changed.
>
> They are ahead of the bytecode, not the native code.
They were ahead of the native code, which was between C++ and SML/NJ.
I even clicked the link and scratched my head over the raw scores,
which seemed to indicate that it should've had a better overall score.
> Again, it's not a promotion site for OCaml. So don't expect it to
> present
> Caml better than any other language.
Actually, since the original shootout author is a fan of OCaml, I
suspect the tests have something of a pro-OCaml bias. ;-)
> So why don't you start your own site, or BETTER : contribute to the
> work
> allready started ?
Every time I start writing a comparison of programming languages, it
seems to require the length of a book...
-------------------
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
next prev parent reply other threads:[~2004-06-19 11:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 18:05 Brian Hurt
2004-06-18 1:18 ` Yaron Minsky
2004-06-18 9:37 ` Sebastien Ferre
2004-06-18 15:45 ` Brian Hurt
2004-06-18 21:39 ` Eray Ozkural
2004-06-18 6:09 ` Brandon J. Van Every
2004-06-18 7:56 ` Ville-Pertti Keinonen
2004-06-18 8:59 ` skaller
2004-06-18 9:57 ` Ville-Pertti Keinonen
2004-06-18 10:48 ` Implementing DSLs in OCaml/CamlP4 (was: Re: [Caml-list] Great Programming Language Shootout Revived) Richard Jones
2004-06-18 12:32 ` Walid Taha
2004-06-18 15:38 ` [Caml-list] Great Programming Language Shootout Revived Brian Hurt
2004-06-18 17:07 ` David Brown
2004-06-19 0:26 ` Nicolas FRANCOIS
2004-06-19 9:04 ` [Caml-list] Benchmark suggestion (Was: Programming Language Shootout) Wolfgang Müller
2004-06-19 10:54 ` Ville-Pertti Keinonen
2004-06-19 19:38 ` [Caml-list] Benchmark suggestion Brandon J. Van Every
2004-06-19 20:08 ` Brian Hurt
2004-06-19 20:16 ` Wolfgang Müller
2004-06-20 11:24 ` [Caml-list] Evangelism Brandon J. Van Every
2004-06-19 11:18 ` Ville-Pertti Keinonen [this message]
2004-06-19 11:56 ` [Caml-list] Great Programming Language Shootout Revived Nicolas Janin
2004-06-19 12:51 ` Marcin 'Qrczak' Kowalczyk
2004-06-19 19:46 ` Brandon J. Van Every
2004-06-19 20:19 ` Brian Hurt
2004-06-19 12:09 ` Nicolas Janin
2004-06-19 12:48 ` John Hughes
2004-06-19 18:57 ` Brian Hurt
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=6D5202BA-C1E2-11D8-B4A4-000393863F70@exomi.com \
--to=will@exomi.com \
--cc=caml-list@inria.fr \
--cc=nicolas.francois@free.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