Re: Test for constant (or "in parameter" in procedure)

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

On 2017-02-09 17:59, reinkor wrote:
> On Thursday, February 9, 2017 at 5:51:46 PM UTC+1, G.B. wrote:
>> On 09.02.17 13:46, reinkor wrote:
>>> OK, I here try to communicate my intention via this simple example:
>>>
>>> i : Constant Integer := 5; -- all OK so far (but someone could
>>>                                change this to a variable)
>>>
>>
>> You could try making it more difficult for programmers
>> you seemingly need to fight in source text by
>>
>> - by making i a function; hide its body,
>> - make your code depend on compile time static constants.
>>
>> I'd suggest that it is time, technically, for your boss
>> or for yourself to call for discipline, or ask you lawyer
>> about what your contracts require you to guarantee if
>> someone changes i to be some kind of constness backdoor.
>
> Maybe SPARK has an answer.

Rather the OS. Set the ads file read-only. Calculate its signature (of 
military-grade length). Store the signature on an encrypted flash drive 
protected by biometric scanner. Verify the signature each 5 seconds to 
detect malicious source code modifications by intruders...

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