Re: [Boost-users] Boost 1.68.0 - boost hashing changed ?

Subject: Re: [Boost-users] Boost 1.68.0 - boost hashing changed ?
From: Shailja Prasad (shalja.rudra_at_[hidden])
Date: 2018-10-24 10:07:14

> On Oct 23, 2018, at 10:11 AM, Miguel Ojeda via Boost-users <boost-users_at_[hidden]> wrote:
> 
>> On Tue, Oct 23, 2018 at 12:36 PM degski <degski_at_[hidden]> wrote:
>> 
>>> On Tue, 23 Oct 2018 at 11:25, Miguel Ojeda <miguel.ojeda.sandonis_at_[hidden]> wrote:
>>> 
>>>> Well, uhm, because that seems to be quite handy. All NIST implementations do exactly this.
>>> 
>>> No, sorry, that is a completely different use case. Crypto hashes are
>>> used, among other things, in network communications, persistent
>>> storage, etc. They need to be "fixed" functions, and their standards
>>> provide the exact definition. That is not the case at all with
>>> std::hash or Boost.Hash.
>> 
>> 
>> For debugging purposes, a fixed function seems quite useful to me.
> 
> Indeed, that is a good point! An std implementation (and Boost.Hash
> too) could provide the means to fix the function for debugging (e.g.
> through a #define).
> 
Ok, tried few approach to get the same hashCode using boost 1.68.0 which is coming from using boost 1.53.0 ( same machine and compiler) looking into your suggested change link. Thank you, Miguel ! 

> Cheers,
> Miguel
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> https://lists.boost.org/mailman/listinfo.cgi/boost-users