From: Dave Mason <dmason@sarg.Ryerson.CA>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: caml-list@inria.fr
Subject: Re: Syntax for label, NEW PROPOSAL
Date: Fri, 17 Mar 2000 12:34:31 -0500 [thread overview]
Message-ID: <200003171734.MAA28829@sarg.Ryerson.CA> (raw)
In-Reply-To: Your message of "Fri, 17 Mar 2000 18:48:40 +0900." <20000317184840K.garrigue@kurims.kyoto-u.ac.jp>
>>>>> On Fri, 17 Mar 2000 18:48:40 +0900, Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp> said:
> Having seen a number of recent messages against having labels in the
> standard library, I have the feeling that there is a lot of
> confusion here, and I would like to make a few points clear.
> * In default (classic) mode, writing labels is (and will stay) not
> required. For those users that do not like labels, or do not want to
>[...]
> * What we are discussing about is modern mode. This is not pedantic
> mode, this is just another typing discipline. This basically doesn't
> concern people who are not very fond of labels, and will be
> perfectly happy with classic mode.
I have been following this discussion somewhat remotely. I've not
been able to do much programming lately, and almost no OCAML (I have
dabbled with Olabl a few times). From what I can see:
1) please do not call it ``modern'' mode. Call it ``label'' mode.
The word modern has baggage attached to it. Other words that would
be as good but also have (somewhat different) baggage include:
different, changed, messed-up, experimental... My point is that we
should use a word that is not ``good'' or ``bad'', and calling it
``label'' mode seems best. I have no opinion on what ``classic''
mode should be called, although I think ``classic'' is fine (there
is a little baggage, but it is split between has-withstood-the-
test-of-time and old-fashioned, so is fairly neutral overall).
2) I do not expect to use label mode very frequently, except when
dealing with ugly APIs (typically ones imported from some outside
world, such as Tk). If I can, in classic mode, program as I always
have done, and access these APIs, but otherwise ignore labels
(especially in the standard libraries!), I will be happy.
3) I hope classic mode will remain the default for a *long* time.
../Dave
next prev parent reply other threads:[~2000-03-17 18:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-15 20:40 Don Syme
2000-03-17 9:48 ` Jacques Garrigue
2000-03-17 17:34 ` Dave Mason [this message]
2000-03-18 0:26 ` Jacques Garrigue
2000-03-23 13:07 ` Sven LUTHER
-- strict thread matches above, loose matches on Subject: below --
2000-03-17 21:33 Damien Doligez
2000-03-18 21:07 ` Frank Atanassow
2000-03-18 22:40 ` John Prevost
2000-03-17 17:03 Don Syme
2000-03-17 19:24 ` John Prevost
2000-03-14 16:53 Syntax for label Don Syme
2000-03-15 3:15 ` Syntax for label, NEW PROPOSAL Jacques Garrigue
2000-03-15 6:58 ` Christophe Raffalli
2000-03-15 21:54 ` Julian Assange
2000-03-15 11:56 ` Wolfram Kahl
2000-03-15 13:58 ` Pierre Weis
2000-03-15 15:26 ` Sven LUTHER
2000-03-17 7:44 ` Pierre Weis
2000-03-15 17:04 ` John Prevost
2000-03-17 10:11 ` Jacques Garrigue
2000-03-15 17:06 ` Markus Mottl
2000-03-15 19:11 ` Remi VANICAT
2000-03-17 8:30 ` Pierre Weis
2000-03-17 14:05 ` Jacques Garrigue
2000-03-17 16:08 ` Pierre Weis
2000-03-15 21:30 ` John Max Skaller
2000-03-16 2:55 ` Jacques Garrigue
2000-03-17 15:13 ` Pierre Weis
2000-03-17 17:33 ` Wolfram Kahl
2000-03-18 11:59 ` Jacques Garrigue
2000-03-21 16:51 ` Pascal Brisset
2000-03-23 11:14 ` Nicolas barnier
2000-03-16 8:50 ` Pascal Brisset
2000-03-17 11:15 ` Sven LUTHER
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=200003171734.MAA28829@sarg.Ryerson.CA \
--to=dmason@sarg.ryerson.ca \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
/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