From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] An extended comparative study of language support for generic programming
Date: Thu, 11 Feb 2010 01:31:00 +0000 [thread overview]
Message-ID: <201002110131.00415.jon@ffconsultancy.com> (raw)
In-Reply-To: <91a2ba3e1002101500x75733e88x2f582a2354742ce4@mail.gmail.com>
On Wednesday 10 February 2010 23:00:44 Raoul Duke wrote:
> > http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.110.122&rep=rep1
> >&type=pdf
> >
> :-)
>
> http://groups.google.com/group/comp.lang.functional/browse_thread/thread/d6
>54fedd6efdf753/3ee82770d5e79402#3ee82770d5e79402
See my response there:
http://groups.google.com/group/comp.lang.functional/msg/2cb15a6281087b04
:-)
I was wondering if anyone here was familiar with this work and/or had anything
to say about their OCaml solutions and discussion?
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
next prev parent reply other threads:[~2010-02-11 0:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-11 0:06 Jon Harrop
2010-02-10 23:00 ` [Caml-list] " Raoul Duke
2010-02-11 1:31 ` Jon Harrop [this message]
2010-02-11 2:10 ` Peng Zang
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=201002110131.00415.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--cc=caml-list@yquem.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;
as well as URLs for NNTP newsgroup(s).