[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABtNtWE6SDo3uD2TpeVtqAbERHarCvez0A08n51Dx+X8QCBVBg@mail.gmail.com>
Date: Sat, 22 Aug 2015 09:59:32 +0800
From: Kai Zhao <loverszhao@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: The cmp_all() of cq
Hi Alexander,
On Sat, Aug 22, 2015 at 9:20 AM, Solar Designer <solar@...nwall.com> wrote:
>
> In fact, if you keep it aggressive, it makes sense to make it even more
> so: print a warning if _any_ one (or more) of cmp_all(), cmp_one(), or
> cmp_exact() reports a possible match when no match is expected. For
> cmp_exact() this would be a fatal error (test failed) unless
> FMT_NOT_EXACT is set, but for cmp_all() or cmp_one() merely a warning,
> which might be a false positive (yet should be printed).
Good solution. I will do this.
Thanks,
Kai
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
