Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!killer!mit-eddie!rutgers!aramis.rutgers.edu!webber
From: webber@aramis.rutgers.edu (Bob Webber)
Newsgroups: comp.misc
Subject: Re: Basics of Program Design
Message-ID: 
Date: 10 Jul 88 04:37:04 GMT
References: <807@vax.UUCP> <440@proxftl.UUCP>
Distribution: na
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 19

In article <440@proxftl.UUCP>, bill@proxftl.UUCP (T. William Wells) writes:
> In article <807@vax.UUCP>, larry@merlin.cvs.rochester.edu (Lawrence Snyder) writes:
<...
< On UNIX, there is also another program `tcov' which is also
< useful.  This program gives you the number of times that each
< statement of a program is executed. While this does not tell you
< how long the statements took, it does give you a good idea where
< to look for inefficiencies.

Err, tcov was actually designed for something slightly different, test
coverage analysis.  The idea is that you might want to test out all that
spiffy code to make sure it works and tcov would tell you which chunks
of code your tests haven't yet executed.  Believe it or not, alot of
commericial code makes it out the door with remarkably few execution
paths tested (for that matter, alot makes it out the door with known
bugs because of deadlines, but that is another matter, at least it
runs fast, sometimes).

----- BOB (webber@athos.rutgers.edu ; rutgers!athos.rutgers.edu!webber)