Bilal,
By "code coverage" I actually was referring to a feature that keeps track of
which lines of source code have been executed at run-time. This lets you see
which lines of code you've actually tested (so you can know if your test suite
was thorough or not) and it can also be useful for finding out which lines of
code may have executed just prior to trapping an event (e.g. hitting a
breakpoint). I know CVI has some very useful features like run-time array index
bounds-checking, null-pointer dereference checking and the like that are usually
associated with "safe" languages like Java and since there are code coverage
analysis tools for Java (e.g. http://www.thecortex.net/clover/ ) I thought CVI
might have it. Is there any documentation on exactly what run-ti
me safety and
sanity checking CVI has?
Nick
