caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Alexander V.Voinov" <avv@quasar.ipa.nw.ru>
To: Gerard.Huet@inria.fr
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] CamlP4 Revised syntax comment
Date: Tue, 29 Oct 2002 10:47:03 -0800 (PST)	[thread overview]
Message-ID: <20021029.104703.59470751.avv@quasar.ipa.nw.ru> (raw)
In-Reply-To: <57FACEC6-EB6A-11D6-A87E-0003938819CE@inria.fr>

Hi 

From: Gérard Huet <Gerard.Huet@inria.fr>
Subject: Re: [Caml-list] CamlP4 Revised syntax comment
Date: Tue, 29 Oct 2002 19:15:02 +0100

> >> match a with
> >> | 0 ->
> >> | n ->
> >> end
> >
> > I second this.
> >
> > Alexander
> >
> 
> Frankly,
> I do not think that design of a programming language (or any reasonably 
> complex
> scientific activity) can be seriously accomplished by exchanges through a
> large mailing list using random criteria of taste and distaste. 

I agree completely. Here I only meant that a closing 'parenthesis' for
the match construction is desired. I don't use revised syntax and don't know it,
but in the standard syntax you have to use parentheses over the entire 'match...'
to resolve ambiguity.

Of course a masterpiece cannot be created by a referendum. :-)

> I personally believe that syntax, and notation in general, is important. 

Me too. BTW quite recently I made a presentation on FP in my company,
and one slide just showed two equivalent programs in Python and OCaml
side by side. This slide was crucial in the overall receiption of the
presentation.  My colleagues got a feeling that FP is not _that_ weird
(as one would infer from the previous slides ;-) after all. (Here in
biotech we use Python very intensively.)

> Important
> for guiding intuition consistently with the semantics, 

Especially when you promote the language among skillful users of some
other language be it C or Ada or Python.

WBR

Alexander
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2002-10-29 19:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-25 19:02 brogoff
2002-10-25 19:25 ` Oleg
2002-10-26  9:27 ` Stefano Zacchiroli
2002-10-26 11:19   ` Daniel de Rauglaudre
2002-10-26 17:38   ` David Brown
2002-10-26 19:27     ` brogoff
2002-10-28  8:38   ` Kontra, Gergely
2002-10-28  9:28     ` Oleg
2002-10-28  9:41       ` Florian Douetteau
2002-10-28 10:04       ` Stefano Zacchiroli
2002-10-28 12:20     ` Daniel de Rauglaudre
2002-10-28 16:53       ` brogoff
2002-10-28 16:56     ` Alexander V.Voinov
2002-10-29 18:15       ` Gérard Huet
2002-10-29 18:47         ` Alexander V.Voinov [this message]
2002-10-29 20:53           ` Damien Doligez
2002-10-29 21:30             ` M E Leypold @ labnet
2002-10-29 21:42         ` brogoff
2002-10-29 11:30 ` Pierre Weis
2002-10-29 16:48   ` brogoff
2002-10-29 17:20     ` Alessandro Baretta
2002-10-30 17:49 Arturo Borquez
2002-10-31  9:21 ` Daniel de Rauglaudre

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=20021029.104703.59470751.avv@quasar.ipa.nw.ru \
    --to=avv@quasar.ipa.nw.ru \
    --cc=Gerard.Huet@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;
as well as URLs for NNTP newsgroup(s).