From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "caml" <caml-list@inria.fr>
Subject: RE: [Caml-list] Great Programming Language Shootout Revived
Date: Sat, 19 Jun 2004 12:46:25 -0700 [thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDOEBAHEAB.vanevery@indiegamedesign.com> (raw)
In-Reply-To: <1087649466.5274.71.camel@qrnik>
Marcin 'Qrczak' Kowalczyk
>
> I think token count is the most objective measure from measures which
> are reasonably easy to take automatically. If not token count, then
> line count, and finally character count.
I don't suppose you guys would consider moving this discussion to
comp.benchmarks? Not so much that it's off-topic on caml-list - I don't
care. Rather, there's this whole community that deals with all these
"are tokens or LOCs better?" issues in exceeding detail, and you're only
repeating what's been done to death in their archives. If you actually
want to design a 'better' language benchmarker, this would be your ideal
watering hole.
Personally I think the idea of 'token counts' is silly, just not as
silly as LOC. How would you ever objectively define the semantic value
of a 'token' ? What if my tokens are more dense with information than
your tokens? Anyways, my question is rhetorical. I suggest
comp.benchmarks.
Cheers, www.indiegamedesign.com
Brandon Van Every Seattle, WA
20% of the world is real.
80% is gobbledygook we make up inside our own heads.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.708 / Virus Database: 464 - Release Date: 6/18/2004
-------------------
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 19:37 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 ` [Caml-list] Great Programming Language Shootout Revived Ville-Pertti Keinonen
2004-06-19 11:56 ` Nicolas Janin
2004-06-19 12:51 ` Marcin 'Qrczak' Kowalczyk
2004-06-19 19:46 ` Brandon J. Van Every [this message]
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=OOEALCJCKEBJBIJHCNJDOEBAHEAB.vanevery@indiegamedesign.com \
--to=vanevery@indiegamedesign.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