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. -- http://mail.python.org/mailman/listinfo/python-list
