caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Frederic van der Plancke <fvdp@decis.be>
To: caml-list@pauillac.inria.fr
Subject: [Caml-list] { ... } vs ( ... ) vs begin ... end
Date: Thu, 10 Apr 2003 09:58:44 +0200	[thread overview]
Message-ID: <3E952434.68E8CD14@decis.be> (raw)
In-Reply-To: <87smsrukf6.fsf@cs.uga.edu>



> Brian Hurt <brian.hurt@qlogic.com> writes:
> 
> > On Tue, 8 Apr 2003, Daniel Andor wrote:
> >
> >> On Tuesday 08 April 2003 8:04 pm, Brian Hurt wrote:
> >> > If we're going to be introducing gratuitous backwards incompatiblities,
> >> > can we please do it for something usefull?  Like say replacing begin/end
> >> > with { and }.
> >>
> >> If I may be a beginner here: how does "begin ... end" differ from "( ... )"?
> >> In practice I've found them to be interchangable, but that could just be an
> >> accident.

No, that's by design AFAIK. I'm no longer using begin-end, because I like 
punctuation to be light on the eye.

> >
> > At the linguistic level, not at all.  At the text editor level, it's
> > easier in vi to jump to match braces than matching begin/ends.

You seem to have missed the difference between ( ... ) and { ... }, the
message you answered used the first form.

There's a big problem with introducing { ... } as synonymous for begin-end:
constructs like  { a = b }  become ambiguous and only the type-checker can
lift the ambiguity.

Frédéric vdP

-------------------
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:[~2003-04-10  7:49 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 12:56 [Caml-list] single-line comment request Nickolay Semyonov-Kolchin
2003-04-08 15:17 ` Samuel Lacas
2003-04-08 14:27   ` Nickolay Semyonov-Kolchin
2003-04-08 16:21     ` Samuel Lacas
2003-04-09 15:15   ` Thierry SALSET
2003-04-08 15:19 ` Brian Hurt
2003-04-08 14:25   ` Nickolay Semyonov-Kolchin
2003-04-08 16:08     ` Brian Hurt
2003-04-08 15:38       ` Nickolay Semyonov-Kolchin
2003-04-08 17:42         ` Brian Hurt
2003-04-08 17:31     ` Chris Hecker
2003-04-08 16:29       ` Nickolay Semyonov-Kolchin
2003-04-08 19:26         ` Basile STARYNKEVITCH
2003-04-08 20:22           ` Brian Hurt
2003-04-08 21:37             ` Michal Moskal
2003-04-08 17:13       ` Brian Hurt
2003-04-08 19:23         ` Chris Hecker
2003-04-08 18:49           ` Karl Zilles
2003-04-08 19:04           ` Brian Hurt
2003-04-08 21:57             ` Daniel Andor
2003-04-08 22:07               ` Michal Moskal
2003-04-08 22:09               ` Brian Hurt
2003-04-10  2:59                 ` cashin
2003-04-10  7:58                   ` Frederic van der Plancke [this message]
2003-04-08 19:42           ` Daniel M. Albro
2003-04-08 18:53             ` Alexander V. Voinov
2003-04-08 18:19               ` Nickolay Semyonov-Kolchin
2003-04-08 22:40             ` Joshua Scholar
2003-04-13 19:46             ` Andreas Rossberg
2003-04-13 22:57               ` Daniel M. Albro
2003-04-08 19:53           ` Jeff Henrikson
2003-04-08 20:31             ` Brian Hurt
2003-04-13 14:07     ` John Max Skaller
2003-04-08 15:28 ` Damien
2003-04-08 14:49   ` Nickolay Semyonov-Kolchin
2003-04-08 15:39   ` Brian Hurt
2003-04-08 15:45   ` malc
2003-04-08 15:45   ` Samuel Lacas

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=3E952434.68E8CD14@decis.be \
    --to=fvdp@decis.be \
    --cc=caml-list@pauillac.inria.fr \
    --cc=fplancke@hotmail.com \
    /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).