From: Jacques Carette <carette@mcmaster.ca>
To: Alwyn Goodloe <agoodloe@seas.upenn.edu>
Cc: Oliver Bandel <oliver@first.in-berlin.de>, caml-list@inria.fr
Subject: Re: [Caml-list] Design-by-contract and Type inference?
Date: Tue, 06 Feb 2007 16:50:11 -0500 [thread overview]
Message-ID: <45C8F813.7050909@mcmaster.ca> (raw)
In-Reply-To: <7009B5BE-ABF2-42B7-9419-84B48ECD4A25@seas.upenn.edu>
More than "some work". I talked with her at PEPM (right before POPL),
and ESC/Haskell is very much alive, and very cool. Details available at
http://www.cl.cam.ac.uk/~nx200/
ESC/Ocaml for the 'functional core' should be straightforward enough
but, as usual, the imperative features make life considerably more complex.
Jacques
Alwyn Goodloe wrote:
> In a related note I believe a student at Cambridge University
> has done some work on ESC/Haskell that would support
> design by contract for Haskell. This leads one to believe that
> one could probably build a version of ESC for OCAML.
>
> Alwyn
>
>
prev parent reply other threads:[~2007-02-06 21:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 5:04 Programming with correctness guarantees oleg
2007-02-01 8:45 ` Andrej Bauer
2007-02-01 13:00 ` [Caml-list] " Chris King
2007-02-01 20:39 ` Jean-Christophe Filliatre
2007-02-01 13:07 ` [Caml-list] " Joshua D. Guttman
2007-02-01 20:12 ` Jean-Christophe Filliatre
2007-02-01 20:35 ` Robert Fischer
2007-02-01 20:57 ` Jean-Christophe Filliatre
2007-02-02 5:47 ` skaller
2007-02-01 20:43 ` Jacques Carette
2007-02-02 0:38 ` Bob Williams
2007-02-02 14:09 ` Jean-Christophe Filliatre
2007-02-03 8:09 ` Tom
2007-02-04 15:47 ` Design-by-contract and Type inference? David MENTRE
2007-02-04 16:04 ` [Caml-list] " Benedikt Grundmann
2007-02-04 16:35 ` Kenn Knowles
2007-02-06 9:29 ` Hendrik Tews
2007-02-06 20:45 ` Oliver Bandel
2007-02-06 21:35 ` Alwyn Goodloe
2007-02-06 21:50 ` Jacques Carette [this message]
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=45C8F813.7050909@mcmaster.ca \
--to=carette@mcmaster.ca \
--cc=agoodloe@seas.upenn.edu \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/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).