Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!lll-lcc!lll-winken!uunet!steinmetz!ge-dab!codas!ateng!chip
From: chip@ateng.UUCP (Chip Salzenberg)
Newsgroups: comp.unix.questions
Subject: Re: Unix diff(1) algorithm
Message-ID: <153@ateng.UUCP>
Date: 18 Jan 88 16:36:59 GMT
References: <11229@brl-adm.ARPA> <7068@brl-smoke.ARPA> <532@cresswell.quintus.UUCP>
Reply-To: chip@ateng.UUCP (Chip Salzenberg)
Organization: A T Engineering, Tampa, FL
Lines: 11

In article <532@cresswell.quintus.UUCP> ok@quintus.UUCP (Richard A. O'Keefe) writes:
>The trouble with diff(1) is that it assumes that the only changes are
>insertions and deletions.  So if you swap two functions, it reports
>two changes.  The method which appeared in CACM can spot moves as well
>as insertions and deletions.

The "hdiff" program does move detection.  It's in the comp.sources.unix
archives.
-- 
Chip Salzenberg                 UUCP: "{codas,uunet}!ateng!chip"
A T Engineering                 My employer's opinions are a trade secret.
    "Anything that works is better than anything that doesn't."  -- me