From: Hendrik Tews <H.Tews@cs.ru.nl>
To: David MENTRE <dmentre@linux-france.org>
Cc: oleg@pobox.com, caml-list@inria.fr, Andrej.Bauer@fmf.uni-lj.si
Subject: Re: [Caml-list] Design-by-contract and Type inference?
Date: Tue, 06 Feb 2007 10:29:10 +0100 [thread overview]
Message-ID: <wwu4ppzr5w9.fsf@tandem.cs.ru.nl> (raw)
In-Reply-To: <87fy9lhql7.fsf@linux-france.org> (David MENTRE's message of "Sun, 04 Feb 2007 16:47:48 +0100")
David MENTRE <dmentre@linux-france.org> writes:
Does anybody know if there is research on design-by-contract (as used in
Eiffel or Spark) and type inference (as used in OCaml)? For example,
relationships between both mechanisms, how the compiler could infer
contracts for a sub-class of a class, how contracts can be maintained
with minimal work from the programmer (a very useful property of ML type
inference), how contract can be statically checked using type inference
information, etc.
JML for Java is similar to what Eiffel provides. There are a lot
of tools for JML, for instance ESC/Java for automatics static
checks.
Hendrik
next prev parent reply other threads:[~2007-02-06 9:29 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 [this message]
2007-02-06 20:45 ` Oliver Bandel
2007-02-06 21:35 ` Alwyn Goodloe
2007-02-06 21:50 ` Jacques Carette
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=wwu4ppzr5w9.fsf@tandem.cs.ru.nl \
--to=h.tews@cs.ru.nl \
--cc=Andrej.Bauer@fmf.uni-lj.si \
--cc=caml-list@inria.fr \
--cc=dmentre@linux-france.org \
--cc=oleg@pobox.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;
as well as URLs for NNTP newsgroup(s).