From: Jacques Carette <carette@mcmaster.ca>
To: Pierre Weis <pierre.weis@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] New release of moca
Date: Sun, 29 Apr 2007 10:09:49 -0400 [thread overview]
Message-ID: <4634A72D.907@mcmaster.ca> (raw)
In-Reply-To: <20070427130839.A46C8BC6B@yquem.inria.fr>
Pierre Weis wrote:
> Relational types in Caml
>
Very nice indeed. As a matter of fact, I was just reading (and
enjoying) the ESOP paper in the plane yesterday!
My question is: why is this done as a pre-processor instead of as an
extension of metaocaml? Certainly some of the features of Moca can be
implemented in metaocaml (I have done this myself for rings and
monoids). The added advantage of using metaocaml is, of course, the
types. As a (syntactic) pre-processor, getting good error messages out
of Moca will be rather challenging, no?
Jacques
PS: Genuine question, not criticism.
next prev parent reply other threads:[~2007-04-29 14:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 13:08 Pierre Weis
2007-04-27 14:14 ` [Caml-list] " skaller
2007-04-29 14:09 ` Jacques Carette [this message]
2007-04-29 14:26 ` skaller
2007-04-29 14:32 ` Jacques Carette
2012-06-04 16:17 Pierre Weis
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=4634A72D.907@mcmaster.ca \
--to=carette@mcmaster.ca \
--cc=caml-list@inria.fr \
--cc=pierre.weis@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