From: Nicolas Cannasse <ncannasse@motion-twin.com>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: lukstafi@gmail.com, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] (int * int) <> int*int ?
Date: Fri, 24 Feb 2006 22:39:53 +0900 [thread overview]
Message-ID: <43FF0CA9.8000500@motion-twin.com> (raw)
In-Reply-To: <20060224.111728.88698334.garrigue@math.nagoya-u.ac.jp>
>>>This unfortunate syntax has consequences down to polymorphic variants,
>>>which otherwise could be represented more efficiently.
>>>
>>
>>This is interesting, could you explain it shortly?
>
>
> The tuple based syntax for constructors is ambiguous: there is no way
> to know syntactically whether a constructor takes as argument a tuple
> or separate arguments. This is the reason for this whole discussion.
Yes this is not a very big problem but is quite often reported.
The reason I see is that (int * int) and int * int are perceived the
same because parenthesis are optional when applying the * operator in
calculus.
In order to fix this, I choose to always have parenthesis for multiple
arguments constructors in NekoML :
type a {
A : int;
B : (int , int); // 2 arguments
C : ((int , int)); // 1 tuple argument
}
It is then more easy to understand the difference between B and C,
although this is in the end just a matter of using an appropriate
syntax. The parenthesis are just abusely used in different manners in
most of languages syntax.
Nicolas
next prev parent reply other threads:[~2006-02-24 13:40 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 17:28 Frédéric Gava
2006-02-23 18:33 ` [Caml-list] " Eric Cooper
2006-02-23 19:03 ` Martin Jambon
2006-02-23 19:07 ` Frédéric Gava
2006-02-23 20:15 ` Brian Hurt
2006-02-23 21:30 ` Frédéric Gava
2006-02-23 21:57 ` Brian Hurt
2006-02-23 22:30 ` Frédéric Gava
2006-02-23 22:50 ` Brian Hurt
2006-02-23 23:07 ` Frédéric Gava
2006-02-24 8:38 ` Alessandro Baretta
2006-02-24 12:59 ` Damien Doligez
2006-02-23 18:33 ` Thomas Fischbacher
2006-02-23 18:56 ` David Brown
2006-02-23 19:24 ` Frédéric Gava
2006-02-23 19:37 ` Frédéric Gava
2006-02-23 19:45 ` Frédéric Gava
2006-02-24 0:01 ` Jacques Garrigue
2006-02-24 0:18 ` Lukasz Stafiniak
2006-02-24 2:17 ` Jacques Garrigue
2006-02-24 13:07 ` Alain Frisch
2006-02-25 17:42 ` Vincent Balat
2006-02-25 18:30 ` Nicolas Pouillard
2006-02-25 19:09 ` Richard Jones
2006-03-01 12:48 ` Nicolas Pouillard
2006-02-25 23:17 ` Christophe TROESTLER
2006-03-01 13:01 ` Nicolas Pouillard
2006-02-27 11:14 ` camlp4 renovation [was: [Caml-list] (int * int) <> int*int ?] Hendrik Tews
2006-02-24 13:39 ` Nicolas Cannasse [this message]
2006-02-24 14:49 ` [Caml-list] (int * int) <> int*int ? Frédéric Gava
2006-02-24 8:27 ` also for tagged records? [Was: Re: [Caml-list] (int * int) <> int*int ?] Sebastian Egner
2006-02-24 14:01 ` Thomas Fischbacher
2006-02-23 20:58 ` [Caml-list] (int * int) <> int*int ? Jon Harrop
2006-02-23 21:36 ` Frédéric Gava
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=43FF0CA9.8000500@motion-twin.com \
--to=ncannasse@motion-twin.com \
--cc=caml-list@yquem.inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
--cc=lukstafi@gmail.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