From: Markus Mottl <mottl@miss.wu-wien.ac.at>
To: bdb-as-camluser@netcourrier.com
Cc: caml-list@inria.fr (OCAML)
Subject: Re: RE: reference initialization
Date: Tue, 16 May 2000 00:31:43 +0200 (MET DST) [thread overview]
Message-ID: <200005152231.AAA17997@miss.wu-wien.ac.at> (raw)
In-Reply-To: <mnet1.958398191.29145.bdb-as-camluser@netcourrier.com> from "bdb-as-camluser@netcourrier.com" at May 15, 2000 03:43:11 PM
> To me, neither approach (ML/Java/C) is satisfying. I have the strong
> feeling that the _only_ way that maximum efficiency and safeness can be
> achieved is to let the programmer specify _proofs_ of safeness when it is
> not obvious at the syntaxic or type level.
>
> Are there any languages in which the programmer can indicate proofs of
> safeness (regardless of fitness for a particular purpose) of the program
> he is writing, and let the compiler use these proofs?
It is indeed possible to have a type system that can be used (misused? ;)
to prove just about any property of your program - nearly...
A language that implements this is Cayenne:
http://www.cs.chalmers.se/~augustss/cayenne
The type system of Cayenne is equivalent in power to predicate logic
(pretty expressive). However, this expressiveness is bought with
decidability: it is, of course, impossible to automatically prove
everything without sometimes sending your type checker to Nirvana (or
worse: do something unsound)...
Best regards,
Markus Mottl
--
Markus Mottl, mottl@miss.wu-wien.ac.at, http://miss.wu-wien.ac.at/~mottl
next prev parent reply other threads:[~2000-05-16 8:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-15 13:43 bdb-as-camluser
2000-05-15 22:31 ` Markus Mottl [this message]
2000-05-16 2:06 ` Patrick M Doane
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=200005152231.AAA17997@miss.wu-wien.ac.at \
--to=mottl@miss.wu-wien.ac.at \
--cc=bdb-as-camluser@netcourrier.com \
--cc=caml-list@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