From: John R Harrison <johnh@ichips.intel.com>
To: caml-list@inria.fr
Cc: John Harrison <johnh@ichips.intel.com>
Subject: Re: [Caml-list] Future of labels, and ideas for library labelling
Date: Tue, 03 Apr 2001 09:39:46 -0700 [thread overview]
Message-ID: <200104031639.JAA17657@dhpc0010.pdx.intel.com> (raw)
Like Jean-Christophe Filliatre and Josh Guttman, I'm one of the "silent
majority" who are happy with conventional CAML syntax and have no
inclination to use labels. I can well imagine that labels might provide
valuable documentation in certain situations, but I put more value on the
directness and mathematical elegance of the traditional functional style.
I'm all in favour of OCaml being an exciting vehicle for new programming
language research. This may be partly responsible for its present vitality.
But it's important to remember that some of us were attracted to CAML by
its conceptual simplicity and its efficient and economical implementation,
rather than by any exotic experimental features. So I fully support
Xavier's policy of keeping extensions like labels out of the "core"
language.
Cheers,
John.
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next reply other threads:[~2001-04-03 18:16 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 16:39 John R Harrison [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-17 11:53 Poigné
2001-04-11 10:48 Francois-Rene Rideau
2001-04-04 16:37 Dave Berry
2001-04-03 7:27 Arturo Borquez
2001-03-31 3:40 [Caml-list] Future of labels Yaron M. Minsky
2001-04-02 3:39 ` [Caml-list] Future of labels, and ideas for library labelling Jacques Garrigue
2001-04-02 7:58 ` Judicael Courant
2001-04-02 8:50 ` Markus Mottl
2001-04-02 10:33 ` kahl
2001-04-03 0:35 ` Jacques Garrigue
2001-04-03 1:36 ` Kipton M Barros
2001-04-03 1:52 ` Patrick M Doane
2001-04-03 3:53 ` Jacques Garrigue
2001-04-03 5:10 ` Patrick M Doane
2001-04-03 9:30 ` Jacques Garrigue
2001-04-03 8:52 ` Xavier Leroy
2001-04-03 9:34 ` Judicael Courant
2001-04-03 9:54 ` Jacques Garrigue
2001-04-03 12:59 ` Jean-Christophe Filliatre
2001-04-03 14:06 ` Jacques Garrigue
2001-04-03 14:12 ` Daniel de Rauglaudre
2001-04-03 14:42 ` Claude Marche
2001-04-04 19:18 ` Gerd Stolpmann
2001-04-03 9:55 ` Ohad Rodeh
2001-04-03 12:02 ` Dave Mason
2001-04-03 13:43 ` Francois-Rene Rideau
2001-04-03 14:23 ` Daniel de Rauglaudre
2001-04-03 13:43 ` Frank Atanassow
2001-04-03 13:58 ` Joshua D. Guttman
2001-04-03 16:52 ` Eric C. Cooper
2001-04-09 9:05 ` John Max Skaller
2001-04-09 7:29 ` John Max Skaller
2001-04-03 8:07 ` Judicael Courant
2001-04-03 6:55 ` Chris Hecker
2001-04-09 8:11 ` John Max Skaller
2001-04-09 9:21 ` Jacques Garrigue
2001-04-09 15:06 ` Fergus Henderson
2001-04-10 18:49 ` John Max Skaller
2001-04-09 19:54 ` Chris Hecker
2001-04-10 3:37 ` Jacques Garrigue
2001-04-10 7:42 ` Judicael Courant
2001-04-10 8:25 ` Jacques Garrigue
2001-04-10 8:46 ` Claude Marche
2001-04-10 10:09 ` Jacques Garrigue
2001-04-10 14:42 ` Lionnel Maugis
2001-04-10 9:06 ` François-René Rideau
2001-04-11 15:34 ` Jacques Garrigue
2001-04-11 17:48 ` Dave Mason
2001-04-10 22:43 ` Brian Rogoff
2001-04-11 8:29 ` Jacques Garrigue
2001-04-11 9:44 ` Anton Moscal
2001-04-11 13:16 ` Didier Remy
2001-04-11 15:11 ` Jacques Garrigue
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=200104031639.JAA17657@dhpc0010.pdx.intel.com \
--to=johnh@ichips.intel.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;
as well as URLs for NNTP newsgroup(s).