Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:38073
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.170 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=nNMC9koOywzqaKmPOiABPyhhuypaeHWCLWogCGkrk+v5+baY1K2HGVcWJFccUW/IdZ
         69psuIcpcfM1rl0NxYndN/bqF97OMXK4NdcMCJIywR9EaKqCc+ODvoxdFIKdJ4q/gUaf
         bzKHxW+8mcXhJg88JNTkI/qktXlXTAKH9JahM=
Message-ID: <fe05d1540806020130m44eb8afs92a8257f8e3df1d4@mail.gmail.com>
Date: Mon, 2 Jun 2008 10:30:13 +0200
To: "Derick Rethans" <derick@php.net>
Cc: internals <internals@lists.php.net>, "Sara Golemon" <pollita@php.net>
In-Reply-To: <alpine.DEB.0.98.0806021020480.10214@kossu.ez.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <fe05d1540806011602sb0194b0i6e91a65aa5e85c0@mail.gmail.com>
	 <alpine.DEB.0.98.0806021020480.10214@kossu.ez.no>
Subject: Re: [PHP-DEV] Drop ext/mhash and add an emulation layer in ext/hash (5.3+), call for help
From: pierre.php@gmail.com ("Pierre Joye")

On Mon, Jun 2, 2008 at 10:21 AM, Derick Rethans <derick@php.net> wrote:
> On Mon, 2 Jun 2008, Pierre Joye wrote:
>
>> While working on the windows ports, I asked Sara about the mhash
>> status in regard of the new shiny ext/hash. The plan is to remove
>> ext/hash completely and emulate it in ext/hash to keep the BC. It
>> could even a configuration flag if one likes to be sure to clean his
>> code to use only the hash APIs.
>
> The mhash extension features some more versions of some algorithms:
> http://mhash.sourceforge.net/ But why bother changing it?

Which algo(s) (or algo version) is not supported by ext/hash? I did
not spot one after a quick read.

> I've not heard of any issues about ext/mhash.

My main reasons would be to do not have to maintain ext/mhash and  the
libmhash Windows port.

Cheers,
-- 
Pierre
http://blog.thepimp.net | http://www.libgd.org