Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.programming.threads > #4389 > unrolled thread

More precision , read again..

Back to article view | Back to comp.programming.threads

Contents

  More precision , read again.. Sky89 <Sky89@sky68.com> - 2018-06-06 15:39 -0400

#4389 — More precision , read again..

Hello...

More precision , read again..

This is my last post here on the C++ and C forums, because
i will quit C++ and stop from coding in C++..

I think there is still a "big" problem with C++ and C..

Look at C++ explicit conversion functions, they were introduced in 
C++11, but this doesn't come by "default" in C++, like in modern Object 
Pascal of Delphi and FreePascal and like in ADA , because in C++ you 
have to write explicit conversion functions,  so this is not good for 
reliability in C++, and C++ doesn't by "default" come with range 
checking and Run-time checks that catch conversion from negative signed 
to unsigned and catch arithmetic overflow , you have for example to add 
and use SafeInt library for that, and C++ doesn't by "default" catch 
out-of-bounds indices of dynamic and static arrays this is why C++ is 
not good for reliability.

But Delphi and FreePascal like ADA come with range checking and Run-time 
checks that catch conversion from negative signed to unsigned , and 
catch out-of-bounds indices of dynamic and static arrays and catch 
arithmetic overflow etc. and you can also dynamically catch this 
exception of ERangeError etc. and they do not allow those bad
implicit type conversions of C++ that are not good for reliability.

And you can carefully read the following, it is very important:

https://critical.eschertech.com/2010/07/07/run-time-checks-are-they-worth-it/


And about Escher C++ Verifier, read carefully:

"Escher C Verifier enables the development of formally-verifiable 
software in a subset of C (based on MISRA-C 2012)."

Read here:

http://www.eschertech.com/products/index.php


So it verifies just a "subset" of C, so that's not good for C++
because for other applications that are not a subset of C , it can
not do for example Run-time checks, so we are again into
this problem again that  C++ and C don't have range checking and many 
Run-time checks, so that's not good in C++ and C because it is not good 
for reliability and it is not good for safety-critical systems.


So for all the reasons above , i think i will stop coding in C++ and
i will quit C++.



Thank you,
Amine Moulay Ramdane.

[toc] | [standalone]

Back to top | Article view | comp.programming.threads

csiph-web