Re: Tests in a software release

["Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>]

On 03/11/2017 08:24, G.B. wrote:
> On 31.10.17 09:32, Dmitry A. Kazakov wrote:
> 
>> 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(*).

Yes, as with any bug, the programmer has an undeniable right to 
introduce it.

>> This is called optimization.
> 
> Optimization means that a compiler translates
> source text using different algorithms.

No.

Optimization is varying the implementation within the braces of the 
contract in order to achieve certain goal, e.g. to reduce memory usage.

> Contracts between clients and suppliers do not
> need a compiler.

Removing checks is not related to enforcement of contracts. It is tuning 
the implementation. So long the contract is not violated by that, it is 
all OK. If it gets violation it is a bug. No rocket science here.

>>  The point is that any run-time check is behavior of the callee and 
>> cannot be argued something belonging to the caller or to whatever else.
> 
> Checks have actually belonged to something else,
> on useful hardware, as has been explained in the past.

Has it been explained that some hardware has instruction ADD? Does it 
mean that "+" has no implementation? Whichever way calls to the caller 
are translated is irrelevant. Again, all effect is the implementation. 
There is no anything else.

-- 
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de