Related articles |
---|
Source code comparison tools johnl@iecc.com (John R Levine) (2005-01-19) |
Re: Source code comparison tools derek@knosof.co.uk (Derek M Jones) (2005-01-22) |
Re: Source code comparison tools spencer@panix.com (David Spencer) (2005-01-22) |
Re: Source code comparison tools idbaxter@semdesigns.com (Ira Baxter) (2005-01-22) |
Re: Source code comparison tools debray@CS.Arizona.EDU (2005-01-22) |
From: | David Spencer <spencer@panix.com> |
Newsgroups: | comp.compilers |
Date: | 22 Jan 2005 18:26:27 -0500 |
Organization: | PANIX Public Access Internet and UNIX, NYC |
References: | 05-01-065 |
Keywords: | tools |
Posted-Date: | 22 Jan 2005 18:26:27 EST |
"John R Levine" <johnl@iecc.com> writes:
>I'm working on a project where I'm trying to understand how a program
>evolved. I have a bunch of snapshots of the C source code to work from.
>It's easy enough to use the Unix diff program to compare the snapshots,
>but it's much too low level. If someone changes the name of variable A to
>B, diff sees that as a change every time the variable is referenced, but
>it's really only one change.
Did you try feeding the varous iterations to cflow?
It may filter out too much signal with the noise, but it would show
changes in call flow.
--
dhs spencer@panix.com
Return to the
comp.compilers page.
Search the
comp.compilers archives again.