From: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
To: dmason@sarg.Ryerson.CA
Cc: caml-list@inria.fr
Subject: Re: Syntax for label, NEW PROPOSAL
Date: Sat, 18 Mar 2000 09:26:54 +0900 [thread overview]
Message-ID: <20000318092654O.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: Your message of "Fri, 17 Mar 2000 12:34:31 -0500" <200003171734.MAA28829@sarg.Ryerson.CA>
From: Dave Mason <dmason@sarg.Ryerson.CA>
> 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).
You have a very good point. In fact -modern was chosen arbitrarily
when integrating olabl code in ocaml, and was to be changed
before the release. It might have avoided some confusions.
-labels would be OK. I just avoided it because it seemed to imply that
one couldn't use labels in classic mode, which is not true.
In my opinion -strict or -pedantic would be wrong: this is not the
intended meaning.
> 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.
This is the intended behaviour. If you have problems in accessing
those APIs in classic mode, then this means something should be done
about it in the API. The implementor of a labelled library may not
realise that one parameter order is not so nice, just because he
doesn't care about it.
For instance, if you use LablTk in classic mode, you will have to put
the widget as last parameter in most functions. If you feel this is
weird, then you should report the inconvenience.
> 3) I hope classic mode will remain the default for a *long* time.
There are no plans to change this.
At least a consensus would be needed.
Jacques
next prev parent reply other threads:[~2000-03-21 14:15 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
2000-03-18 0:26 ` Jacques Garrigue [this message]
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=20000318092654O.garrigue@kurims.kyoto-u.ac.jp \
--to=garrigue@kurims.kyoto-u.ac.jp \
--cc=caml-list@inria.fr \
--cc=dmason@sarg.Ryerson.CA \
/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