caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Daniel de Rauglaudre <daniel.de_rauglaudre@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] CamlP4 Revised syntax comment
Date: Sat, 26 Oct 2002 13:19:24 +0200	[thread overview]
Message-ID: <20021026131924.D22900@verdot.inria.fr> (raw)
In-Reply-To: <20021026092737.GC15534@cs.unibo.it>; from zack@cs.unibo.it on Sat, Oct 26, 2002 at 11:27:37AM +0200

Hi,

On Sat, Oct 26, 2002 at 11:27:37AM +0200, Stefano Zacchiroli wrote:

> > comparison, and this change removes that overloading and uses a 
> > fairly common (C, Haskell, Clean,...) symbol == for equality.
> It's an idea that is worth considering. It fits well with the consistent
> use of the other C like operators as "||" and "&&" and the disposal of
> "or".

This is a good idea, indeed, but I have two remarks:

- first, this is more a question of library than syntax; Camlp4 can do
  that, but it is a not really clean. Well, actually, it does it for the
  record label "contents" which is renamed "val" in the revised syntax
  (to be shorter).

- second, it is a semantic change, and if programs using the revised
  syntax used the physical equality ==, this change would change their
  code into normal equality.

Therefore, IMHO, this could be included only if there are several
other changes, a set of several changes being more acceptable.

> >     Another possible change along the same lines is having =/= or /= for 
> > inequality, which happens to look a little more like the mathematical 
> > symbol. 
> Uhm ... I disagree here, changing an operator in favour of a more
> diffused one is comfortable, adopting a new one from scratch just
> because it look more like the mathematical symbol can be really
> confusing ...

I agree with you, for the same reasons.

-- 
Daniel de RAUGLAUDRE
http://cristal.inria.fr/~ddr/
-------------------
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-26 11:19 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 [this message]
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
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=20021026131924.D22900@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;
as well as URLs for NNTP newsgroup(s).