Re: 100%

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jun 23, 2007, 12:21 UTC
Message-ID: <Pine.LNX.4.64.0706231318180.4059@racer.site>
In-Reply-To: <467D0DE8.6030104@lsrfire.ath.cx>

Hi,

On Sat, 23 Jun 2007, René Scharfe wrote:

Show 5 quoted lines

> As I already hinted at, the common result of comparing two files, as 
> done by e.g. cmp(1), is one bit that indicates equality.  This 
> information is lost when using up/down rounding, but it is retained when 
> rounding down.  It's _not_ common to be unable to determine equality 
> from the result of a file compare.

And as _I_ already hinted, this does not matter. The whole purpose to have a number here instead of a bit is to have a larger range. In practice, I bet that the 100% are really uninteresting. At least here, they are.

For example, if you move a Java class from one package into another, you have to change the package name in the file. Guess what, I am perfectly okay if the rename detector says "100% similarity" here. Because if it is closer to 100% than to 99%, dammit, I want to see 100%, not 99%.

Nuff said about this subject.

Ciao, Dscho