Re: test suite progress

On Wed, 25 Apr 2001, Sam TH wrote:

> > With an md5 digest, all you know is that it is wrong, but not how wrong.
>
> I'm not sure we're talking about the same thing.

I realized that just after I posted that mail... I should know better than to
send mails early in the morning! ;-)

I was thinking you wanted to store the md5 hash among the test suite data,
run md5 on data generated in runtime and then compare those.

> Using diff to figure out what went wrong would certainly be possible
> afterwords. It might even be possible to do this once you detect a
> failure. But I'm suggesting that failure detection be done with md5sums,
> not cmp.

So, I'm all for doing md5 comparisons if you are to do many comparisons
between files. For speed.

Sorry for me adding confusion.

-- 
      Daniel Stenberg - http://daniel.haxx.se - +46-705-44 31 77
   ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol