From: Remi VANICAT <vanicat@labri.u-bordeaux.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] :: operator not quotable using ( ... )
Date: 24 Apr 2002 12:56:35 +0200 [thread overview]
Message-ID: <874ri174bg.dlv@wanadoo.fr> (raw)
In-Reply-To: <86662hviil.fsf@laurelin.dementia.org>
John Prevost <visigoth@cs.cmu.edu> writes:
> When writing an example just now for this list, I noticed that you can
> no longer (assuming you ever could) write (::) or any variation
> thereof to refer to the definition of the :: cons operator. Since
> there is no other standard way to write this, one must use:
cons is not really an operator, it's a constructor
>
> let cons x y = x :: y
the same hold for any constructor :
moi@debian:~/prog/ocaml-cvs$ ocaml
Objective Caml version 3.04
# type foo =
Bar of int * int;;
type foo = Bar of int * int
# Bar;;
The constructor Bar expects 2 argument(s),
but is here applied to 0 argument(s)
#
you have to write
let bar x y = Bar (x, y)
>
> to get one. This is unfortunate when you wish to, say, define map in
> terms of fold. My suspicion is that it may have worked in the past,
> but broken by keyword argument parsing. Is there any chance (::)
> could be special cased to work correctly, even though it conflicts
> with (x : y) for typing? I don't think it likely that anybody would
> write (::) intending to express a type.
I don't know, but the true problem is the possibility to implicitly
define function that correspond to constructor.
--
Rémi Vanicat
vanicat@labri.u-bordeaux.fr
http://dept-info.labri.u-bordeaux.fr/~vanicat
-------------------
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
next prev parent reply other threads:[~2002-04-24 10:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-24 4:16 John Prevost
2002-04-24 10:56 ` Remi VANICAT [this message]
2002-04-24 21:11 ` 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=874ri174bg.dlv@wanadoo.fr \
--to=vanicat@labri.u-bordeaux.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