From: "David Allsopp" <dra-news@metastack.com>
To: "'Jon Harrop'" <jon@ffconsultancy.com>, <caml-list@yquem.inria.fr>
Subject: RE: [Caml-list] Constructors are not functions
Date: Tue, 6 Oct 2009 15:04:02 +0100 [thread overview]
Message-ID: <005501ca468d$dc9b51a0$95d1f4e0$@metastack.com> (raw)
In-Reply-To: <200910061415.48065.jon@ffconsultancy.com>
Jon Harrop wrote:
> David Allsopp wrote:
> > I think it would be possible to simulate the SML behaviour in OCaml
> > using camlp4 (if you assume that for [type foo = Bar of int] that future
> > unbound references to [bar] are interpreted as [fun x -> bar x] instead of an
> > error)
>
> Only if you turned multi-argument type constructors into single-
> argument ones
> taking a tuple, i.e. type definitions like:
>
> type t = Bar of int * int
>
> must become:
>
> type t = Bar of (int * int)
That's not the case at all - there'd be no reason not to interpret [bar] as [fun x y -> Bar(x, y)] for [Bar of int * int]. What would be hairy in camlp4 would be having to read .cmi files to deal with types defined outside your source file, but that's still not impossible...
David
next prev parent reply other threads:[~2009-10-06 14:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 12:01 Chantal KELLER
2009-10-06 12:19 ` [Caml-list] " Philippe Wang
2009-10-06 12:38 ` Jon Harrop
2009-10-06 13:38 ` Richard Jones
2009-10-10 11:49 ` blue storm
2009-10-06 12:45 ` David Allsopp
2009-10-06 12:46 ` David Allsopp
2009-10-06 13:14 ` Jim Farrand
2009-10-06 13:51 ` Michel Mauny
2009-10-06 13:15 ` Jon Harrop
2009-10-06 14:04 ` David Allsopp [this message]
2009-10-06 14:51 ` Jon Harrop
2009-10-06 15:24 ` Richard Jones
2009-10-06 16:31 ` Jacques Garrigue
2009-10-08 12:37 ` Goswin von Brederlow
2009-10-09 6:29 ` David Allsopp
2009-10-10 6:16 ` Goswin von Brederlow
2009-10-06 13:18 ` Gerd Stolpmann
2009-10-06 15:50 ` Jérémie Dimino
2009-10-06 21:55 ` blue storm
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='005501ca468d$dc9b51a0$95d1f4e0$@metastack.com' \
--to=dra-news@metastack.com \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.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).