Re: Reply#1 To NIST request about "high integrity" C, C++

Re: Reply#1 To NIST request about "high integrity" C, C++

[Ken Garlington]

Mike Berens wrote:
> 
> NSTEWART@ccmail.dsccc.com wrote:
> 
> If I am not mistaken the Government allegedly solved this problem
> about ten years ago.
> The solution was called Ada.

(The "problem" being a search for tools to use in analyzing 
safety-critical C/C++ code)

Actually, if you look at the list of features desired, Ada doesn't
directly supply all of them. However, there are commercial tools
that can be used to do these type of analyses on Ada code. Ada, of
course, may make it easier to do the analysis, but it doesn't magically
generate all the information on the NIST wish list:

>       dynamic memory allocation, memory paging and swapping,
>       recursive function calls, control flow complexity,
>       interface ambiguities, dynamic binding, tasking, interrupt
>       driven processing, built-in-functions, compiled libraries,
>       mixed language programming, obscure or subtle programming
>       constructs, dispersion of related elements, literals,
>       global variables, complexity of interfaces, anonymous data
>       types, hardware dependencies, parameter passing to
>       routines, data typing, class library size, operator
>       overloading, functions or procedures with side effects,
>       reserved words.

-- 
LMTAS - "Our Brand Means Quality"