Changes between Version 3 and Version 4 of CodeCoverage


Ignore:
Timestamp:
Jul 30, 2008, 12:06:56 AM (11 years ago)
Author:
gz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • CodeCoverage

    v3 v4  
    2424to figure out which logical path through the code was taken and which wasn't.  If that
    2525doesn't work, you can try disassembling to see which parts of the compiled code were
    26 not executed.
     26not executed: in the disassembled code there will be references to `#<CODE-NOTE [`xxx`] ...>`
     27where xxx is NIL if the code that follows was never executed and non-NIL if it was.
    2728
    2829Sometimes the situation can be improved by modifying macros to try to preserve more of the
    2930input forms, rather than destructuring and rebuilding them.
    3031
    31 Coverage information for inlined functions is not reliable.  Currently there is no workaround
    32 short of removing the inline declarations.
    33 
    3432Because the code coverage information is associated with compiled functions, load-time
    35 toplevel expressions may not get reported on. You can work around this by creating a
     33toplevel expressions do not get reported on. You can work around this by creating a
    3634function and calling it.  I.e. instead of
    3735
     
    113111while this variable is true will contain code coverage instrumentation.
    114112
    115 === Example Output ===
     113'''`CCL:WITHOUT-COMPILING-CODE-COVERAGE &body body`'''
    116114
    117 The output produced after loading `CL-PPCRE` and running `(cl-ppcre-test:test)` is [http://openmcl.clozure.com/examples/ppcre.html here].
    118 
    119 The corresponding statistics file is [http://openmcl.clozure.com/examples/statistics.csv here].
     115This macro arranges so that `body` doesn't record internal details of code coverage.  It will be considered totally covered if it's entered at all.  The Common Lisp macros `ASSERT` and `CHECK-TYPE` use this macro.