Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming.threads > #4302
| From | Sky89 <Sky89@sky68.com> |
|---|---|
| Newsgroups | comp.programming.threads |
| Subject | There is still a problem with C++ and C |
| Date | 2018-05-19 13:00 -0400 |
| Organization | A noiseless patient Spider |
| Message-ID | <pdpl7h$6pr$4@dont-email.me> (permalink) |
Hello... There is still a problem with C++ and C 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, so read the following carefully: I think that 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. But C++ and C don't have range checking etc. so that's not good in C++ and C because it is not good for safety-critical systems. You can carefully read the following, it is very important: https://critical.eschertech.com/2010/07/07/run-time-checks-are-they-worth-it/ Thank you, Amine Moulay Ramdane.
Back to comp.programming.threads | Previous | Next | Find similar | Unroll thread
There is still a problem with C++ and C Sky89 <Sky89@sky68.com> - 2018-05-19 13:00 -0400
csiph-web