From: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] variant with tuple arg in pattern match?
Date: Sat, 7 Apr 2001 08:44:48 +0200 [thread overview]
Message-ID: <20010407084448.B8023@verdot.inria.fr> (raw)
In-Reply-To: <Pine.BSF.3.96.1010406213912.16279A-100000@fledge.watson.org>; from patrick@watson.org on Fri, Apr 06, 2001 at 09:42:38PM -0400
Hi,
On Fri, Apr 06, 2001 at 09:42:38PM -0400, Patrick M Doane wrote:
> What are the current thoughts about adopting the revised syntax as the
> "standard one"? How many programmers use that syntax?
Discussions about syntax generally degenerate into quarrels because it
is often a question of taste and find a consensus is extremely hard.
Adopting it as "standard one" is then not possible. And there is too
much code written in OCaml by all users.
I wrote this "revised" syntax but I don't think that many people use
it. I have no idea of the number, but probably very few. Except me, I
just know two persons, one of them already not agreeing one of my
choices. I agree to improve this syntax, to change things (I mean in
the Camlp4 distribution), but only if there are more than 3 persons
interested.
Well, everybody can make his own syntax, e.g. starting from the file
treating the normal syntax (etc/pa_o.ml) or the file of the revised
syntax (meta/pa_r.ml). This revised syntax, even dating from several
years, is just an experiment. I would have liked that people
experiment other possible syntaxes, but it seems that it is not a
subject interesting many people.
Less than genealogy, in any case...
--
Daniel de RAUGLAUDRE
daniel.de_rauglaudre@inria.fr
http://cristal.inria.fr/~ddr/
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-04-07 6:44 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-04 11:04 Chris Hecker
2001-04-04 18:47 ` Alain Frisch
2001-04-04 19:18 ` Patrick M Doane
2001-04-04 19:36 ` Chris Hecker
2001-04-04 19:49 ` Daniel de Rauglaudre
2001-04-05 8:19 ` Christian RINDERKNECHT
2001-04-04 19:49 ` Patrick M Doane
2001-04-06 13:52 ` Xavier Leroy
2001-04-07 1:42 ` Patrick M Doane
2001-04-07 6:44 ` Daniel de Rauglaudre [this message]
2001-04-07 7:42 ` Fergus Henderson
2001-04-08 19:45 ` Pierre Weis
2001-04-08 20:37 ` Charles Martin
2001-04-08 23:57 ` Brian Rogoff
2001-04-09 0:22 ` Alain Frisch
2001-04-09 16:07 ` Pierre Weis
2001-04-10 8:23 ` Michel Mauny
2001-04-10 9:14 ` Xavier Leroy
2001-04-10 10:09 ` Michel Mauny
2001-04-10 10:44 ` reig
2001-04-10 11:32 ` Michel Mauny
2001-04-10 11:47 ` reig
2001-04-10 12:10 ` reig
2001-04-10 12:35 ` Michel Mauny
2001-04-10 12:49 ` Marcin 'Qrczak' Kowalczyk
2001-04-09 6:23 ` Mattias Waldau
2001-04-09 7:34 ` Daniel de Rauglaudre
2001-04-09 15:57 ` Pierre Weis
2001-04-10 9:07 ` Sven LUTHER
2001-04-09 8:20 ` Christian RINDERKNECHT
2001-04-10 2:54 ` Patrick M Doane
2001-04-10 19:04 ` John Max Skaller
2001-04-08 0:22 jgm
2001-04-10 12:17 Dave Berry
2001-04-10 13:12 ` Marcin 'Qrczak' Kowalczyk
2001-04-10 21:26 ` Bruce Hoult
2001-04-10 22:34 ` John Prevost
2001-04-10 13:51 ` Frank Atanassow
2001-04-10 17:25 Dave Berry
2001-04-10 23:16 ` Marcin 'Qrczak' Kowalczyk
2001-04-10 17:33 Dave Berry
2001-04-10 22:34 ` John Prevost
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=20010407084448.B8023@verdot.inria.fr \
--to=daniel.de_rauglaudre@inria.fr \
--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