From: Oleg <oleg_inconnu@myrealbox.com>
To: sajuma@utu.fi
Cc: caml-list@inria.fr
Subject: [Caml-list] productivity improvement (was: Rule based language)
Date: Sat, 27 Jul 2002 05:08:40 -0400 [thread overview]
Message-ID: <200207270907.FAA03871@dewberry.cc.columbia.edu> (raw)
In-Reply-To: <1027549877.3d3f2ab5bff5c@webmail.utu.fi>
On Wednesday 24 July 2002 06:31 pm, sajuma@utu.fi wrote:
> Anyway, problems in memory management and modularity
> only appear when the programs become big. Usually big
> programs are not written in two languages, so comparison
> is hard. But the example of Horus vs. Ensemble shows that
> there is very large improvement.
Do you have links/references? (Although the fact that ML is more productive
than C is quite believable to me) I found Horus/Ensemble web site. It looks
like it has not been updated in 5 years[1]
> [...] why are you using C++?
It's very easy to give simple examples of when C++ is much more productive
than C in programs defined by their I/O (If anyone needs such examples: a)
reverse a file, b) reverse lines in a file c) /usr/bin/sort ). The situation
seems to be different with O'Caml vs C++.
Regards,
Oleg
[1] Maybe the complexity has cought up with them eventually :)
-------------------
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
prev parent reply other threads:[~2002-07-27 9:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-24 22:31 [Caml-list] Rule based language [was: productivity improvement] sajuma
2002-07-25 6:26 ` Oleg
2002-07-25 13:30 ` [Caml-list] Rule based language sajuma
2002-07-25 18:16 ` Oleg
2002-07-25 18:29 ` Francois Rouaix
2002-07-27 9:08 ` Oleg [this message]
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=200207270907.FAA03871@dewberry.cc.columbia.edu \
--to=oleg_inconnu@myrealbox.com \
--cc=caml-list@inria.fr \
--cc=sajuma@utu.fi \
/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).