From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Jacques Carette <carette@mcmaster.ca>
Cc: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Typing Dynamic Typing in ocaml?
Date: Wed, 17 Dec 2008 22:15:43 +0100 [thread overview]
Message-ID: <B559EE14-3014-4670-BBAD-188D4A09F258@erratique.ch> (raw)
In-Reply-To: <49496A5F.5080705@mcmaster.ca>
Le 17 déc. 08 à 22:08, Jacques Carette a écrit :
> Scarily enough, I do believe that that is exactly what I need. I
> guess I was hoping to avoid Obj, but this may be one of those
> instances where it is indeed the most reasonable compromise.
Maybe not. Follow these pointers [1,2].
Best,
Daniel
[1] http://mlton.org/UniversalType
[2] http://ocaml.janestreet.com/?q=node/18
next prev parent reply other threads:[~2008-12-17 21:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 19:45 Jacques Carette
2008-12-17 19:58 ` [Caml-list] " Stéphane Glondu
2008-12-17 21:08 ` Jacques Carette
2008-12-17 21:15 ` Stéphane Glondu
2008-12-17 21:15 ` Daniel Bünzli [this message]
2008-12-17 20:29 ` Mikkel Fahnøe Jørgensen
2008-12-17 21:28 ` David Teller
2008-12-17 22:42 ` Mauricio Fernandez
2008-12-18 1:16 ` Yaron Minsky
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=B559EE14-3014-4670-BBAD-188D4A09F258@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=carette@mcmaster.ca \
/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).