Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:76944
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 209.85.217.171 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53FEE35A.7010402@php.net>
References: <53FEE18E.9070900@php.net> <CAEZPtU6ZJaObDHQ4Qy9X2REEM9+0uneyeDdJXJgQYN2o5zb3_g@mail.gmail.com>
 <53FEE35A.7010402@php.net>
Date: Thu, 28 Aug 2014 17:38:21 +0800
Message-ID: <CABBJUpdUZ0sTiSnRw158WYetqZpK1j5psg-QXwPwB6j=CVAphg@mail.gmail.com>
To: Sebastian Bergmann <sebastian@php.net>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] SipHash
From: laruence@php.net (Xinchen Hui)

On Thu, Aug 28, 2014 at 4:07 PM, Sebastian Bergmann <sebastian@php.net> wrote:
> Am 28.08.2014 um 10:04 schrieb Pierre Joye:
>> ext/hash can have it anyway. I did not look at it if it makes sense to
>> use it in other parts.
>
>  Sorry for not bein more clear: yes, I was thinking about adding it to
>  ext/hash, of course. It might make sense, though, to evaluate whether
>  it can also be used internally. Other languages seem to have switched
>  their hashtable implementation to SipHash.
hmm,

maybe you could do some benchmark on real-apps?

thanks
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>



-- 
Xinchen Hui
@Laruence
http://www.laruence.com/