From: "David McClain" <dmcclain@azstarnet.com>
To: <caml-list@inria.fr>
Subject: Syntax Discussions and Caml Philosophy
Date: Fri, 17 Mar 2000 15:12:08 -0700 [thread overview]
Message-ID: <002401bf905d$d768ef80$250148bf@vega> (raw)
I have been reading the past messages about label syntax with some degree of
interest... I am not expert enough in their use to make any comments
regarding them. But I will echo the experience of a heavy user of Caml in
saying that I have been quite pleased with the "orthogonality" of syntactic
components.
I find that Caml is first among languages (and beyond Lisp) that permit
drastic and radical changes to underlying modules of very large programs
without introducing unwanted side effect propagation. This amazing property
has enabled a tenfold increase in my own productivity. Whatever the outcome
of these discussions, I do hope that these orthogonality goals, and the
other simple "properties" of the language can be maintained. This compiler
is too elegant and useful to destroy with the introduction of intrusive
features...
David McClain, Sr. Scientist
Raytheon Systems Co.
Tucson, AZ
reply other threads:[~2000-03-18 17:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='002401bf905d$d768ef80$250148bf@vega' \
--to=dmcclain@azstarnet.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