[SystemSafety] C++ and Pointers

Robert P. Schaefer rps at mit.edu
Wed Jun 5 14:56:57 CEST 2019


Be aware though the code may be updated, the comments may not be.

Then the problem becomes one of  the man who has two wristwatches.

> On Jun 5, 2019, at 8:40 AM, Peter Bernard Ladkin <ladkin at causalis.com> wrote:
> 
> 
> 
> On 2019-06-05 13:08 , paul_e.bennett at topmail.co.uk wrote:
>> 
>>> [PBL] ..... a readable WWW site introducing C++ ,  
>>> https://www.learncpp.com
>>> .........
>>> 
>>> You need a static analyser just to tell you what your program 
>>> means!
>> 
>> Some of the above should also point out the need to provide some form
>> of in-source documentation that describes what the author intended to
>> be happening within the functionality of the code.
> I agree completely. For example, a programmer could include as a comment the intended code written
> in AdaCore SPARK. Then hisher intent will be quite clear.
> 
> PBL
> 
> Prof. Peter Bernard Ladkin, Bielefeld, Germany
> MoreInCommon
> Je suis Charlie
> Tel+msg +49 (0)521 880 7319  www.rvs-bi.de
> 
> 
> 
> 
> 
> _______________________________________________
> The System Safety Mailing List
> systemsafety at TechFak.Uni-Bielefeld.DE
> Manage your subscription: https://lists.techfak.uni-bielefeld.de/mailman/listinfo/systemsafety



More information about the systemsafety mailing list