C metrics package.

What's where?

    ./Rights - what you can do with this software

    ./Authors - self-serving drivel

    ./README - you are here

    doc/ - various pieces of documentation, including results of some
           experiments

    src/ - source for the various tools.  "cd src; make all"

Problems?

    Ugly code.

    Requires N passes over a file (N == number of tools) to completely
    gather statistics for that file.

    Mccabe uses heuristics to determine start of function.

    Conte, Dunsmore and Shen [see doc/References] suggest that the 
    halstead "n2" "may be useful in identifying at an early stage those
    modules most likely to contain errors" (pg 347).  Currently, the
    halstead model does not print n2.  (This is easy to change, but then
    you need to change the scripts in src/control.)

    My definition of metrics may differ from other sources.

Todo?

    Someone (hint) should modify the front end of a freely redististributable
    compiler to deterministically collect all of these statistics in one
    pass over the source file.

    If you are motivated to do work or have bug fixes, send them to me.

Building a better model.

    If you find that these tools assist you in developing or maintaining
    software, please let me know how.  Also, if you have performed some
    statistical analysis of interest, please let me know.  If there is
    general interest, I will be glad to moderate discussions on using
    software metrics and send out updates and new tools.
