From: Richard Jones <rich@annexia.org>
To: David Allsopp <dra-news@metastack.com>
Cc: 'Jon Harrop' <jon@ffconsultancy.com>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Constructors are not functions
Date: Tue, 6 Oct 2009 16:24:04 +0100 [thread overview]
Message-ID: <20091006152404.GA19326@annexia.org> (raw)
In-Reply-To: <005501ca468d$dc9b51a0$95d1f4e0$@metastack.com>
On Tue, Oct 06, 2009 at 03:04:02PM +0100, David Allsopp wrote:
> 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...
The devil is in the details. I had a look at this, and because you
don't have access to the command line (eg. -I parameters) you can't
easily find the *.cmi files you need. That is assuming it was easy to
parse the command line (hard to do it reliably) or that you could look
inside *.cmi files (the format is undocumented and release-specific).
It would be so nice to have a macro tool which was aware of types, but
that tool isn't camlp4. There are probably theoretical problems with
this, but having a "give_me_the_type_of (ocaml_subexpression)"
function would be awesome indeed.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2009-10-06 15:24 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
2009-10-06 14:51 ` Jon Harrop
2009-10-06 15:24 ` Richard Jones [this message]
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=20091006152404.GA19326@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@yquem.inria.fr \
--cc=dra-news@metastack.com \
--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