Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:44095 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 38308 invoked from network); 29 May 2009 23:30:02 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 May 2009 23:30:02 -0000 Authentication-Results: pb1.pair.com smtp.mail=shire@tekrat.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=shire@tekrat.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain tekrat.com from 208.43.138.18 cause and error) X-PHP-List-Original-Sender: shire@tekrat.com X-Host-Fingerprint: 208.43.138.18 sizzo.org Linux 2.6 Received: from [208.43.138.18] ([208.43.138.18:54280] helo=sizzo.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E1/09-28084-9FF602A4 for ; Fri, 29 May 2009 19:30:02 -0400 Received: from shirebook.local (unknown [75.101.56.2]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by sizzo.org (Postfix) with ESMTPSA id CD467CBE525; Fri, 29 May 2009 16:29:58 -0700 (PDT) Message-ID: <4A206FF3.7090806@tekrat.com> Date: Fri, 29 May 2009 16:29:55 -0700 User-Agent: Postbox 1.0b12 (Macintosh/2009051120) MIME-Version: 1.0 To: =?UTF-8?B?Q3Jpc3RpYW4gUm9kcsOtZ3Vleg==?= CC: internals@lists.php.net References: <4A1BDCF3.1020703@gmx.net> <4A1FDA44.7060808@suse.de> In-Reply-To: <4A1FDA44.7060808@suse.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [PHP-DEV] Removing zend_hash_func in PHP 6.0 From: shire@tekrat.com (shire) Cristian Rodríguez wrote: > David Soria Parra escribió: >> Hi List, >> >> I recently discovered that zend_hash_func is equal to >> zend_get_hash_value. To clean this up, I would like to remove >> zend_hash_func in favor of zend_get_hash in HEAD. If there are no >> objections I would commit a patch in a few days. > > We can start with the attached patch and then remove it in the future... Yeah, althoughI would suggest we put this patch as a TODO for php-5.4, and then completely remove it in 6 -shire