caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nicolas Janin" <Ninja40@ifrance.com>
To: "Nicolas FRANCOIS \(AKA El Bofo\)" <nicolas.francois@free.fr>,
	<caml-list@inria.fr>
Subject: Re: [Caml-list] Great Programming Language Shootout Revived
Date: Sat, 19 Jun 2004 14:09:41 +0200	[thread overview]
Message-ID: <008401c455f6$51c5f4a0$9a823951@Pif> (raw)
In-Reply-To: <20040619022648.7864665d.nicolas.francois@free.fr>

Thinking about it a little more, the good thing with LOC count is, as I've
read somewhere else, in large softwares (say > 50,000 LOC), LOC count was
quite a fairly good measure of the size of a project in terms of spent
resources. In other words, according to surveys, the effort involved (as
measured in man-months) was fairly proportional to the LOC count, which is
why LOC count still prevails as a measurement of a software project.
However there has never been any survey measuring code size in terms of
zipped kilobytes unfortunately, although one might suspect the correlation
between this measurement and the effort involved would be stronger than with
LOC count.

Also, it is not obvious at all how this translates to small programs of <200
lines like in the shootout.


___[ Pub ]____________________________________________________________
Inscrivez-vous gratuitement sur Tandaime, Le site de rencontres !
http://rencontre.rencontres.com/index.php?origine=4

-------------------
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:[~2004-06-19 12:09 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
2004-06-19 20:19           ` Brian Hurt
2004-06-19 12:09     ` Nicolas Janin [this message]
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='008401c455f6$51c5f4a0$9a823951@Pif' \
    --to=ninja40@ifrance.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;
as well as URLs for NNTP newsgroup(s).