Re: Tests in a software release

[G. B. <nonlegitur@nmhp.invalid>]

Randy Brukardt <randy@rrsoftware.com> wrote:
> "G.B." <bauhaus@notmyhomepage.invalid> wrote in message 
> news:oth5k4$eih$1@dont-email.me...
> ...
>>> Checks can be removed only when statically proven not to fail.
>> 
>> Programmers may remove checks whenever they think
>> they should. No fancy proof is required(*).
> 
> Such programmers should be fired at the earliest opportunity.

When I, the programer who knows he is obeying
the clause of the contract that my company and
the supplier‘s have both signed (sic), then the
other party insisting that we should nevertheless 
run their checks does not abide.

And is giving an interesting impression of their
understanding of both contracts and quality.

> That turns Ada 
> into an inferior version of C.

Contracts remove needs for talking about 
what can so easily go wrong in C, because that
has already been talked about and written down
as a contract clause. Ada types and compilers
do help, but only so much.

The most important thing is, designing by contract 
is *not* programming defensively. By definition.