--- On Sun, 9/12/10, Paul Rubin <no.em...@nospam.invalid> wrote:
> From: Paul Rubin <no.em...@nospam.invalid>
> Subject: Re: Static typing, Python, D, DbC
> To: python-list@python.org
> Date: Sunday, September 12, 2010, 4:28 PM
> Bearophile <bearophileh...@lycos.com>
> writes:
> > I see DbC for Python as a way to avoid or fix some of
> the bugs of the
> > program, and not to perform proof of correctness of
> the code. Even if
> > you can't be certain, you are able reduce the
> probabilities of some
> > bugs to happen.
>
> I think DbC as envisioned by the Eiffel guy who coined (and
> trademarked)
> the term is that it's a static verification technique,
> marketing-speak
> annotating subroutines with pre- and post- conditions that
> can be
> checked with Hoare logic. Runtime checks wouldn't
> qualify as that.
Eiffel throws an exception when a contract is violated. That is run time
behavior, not static verification.
-EdK
Ed Keith
e_...@yahoo.com
Blog: edkeith.blogspot.com
--
http://mail.python.org/mailman/listinfo/python-list
