Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:36167 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 90217 invoked from network); 17 Mar 2008 12:20:59 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 17 Mar 2008 12:20:59 -0000 Authentication-Results: pb1.pair.com header.from=ilia@prohost.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=ilia@prohost.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain prohost.org from 64.233.166.181 cause and error) X-PHP-List-Original-Sender: ilia@prohost.org X-Host-Fingerprint: 64.233.166.181 py-out-1112.google.com Received: from [64.233.166.181] ([64.233.166.181:19455] helo=py-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9D/55-62762-9226ED74 for ; Mon, 17 Mar 2008 07:20:57 -0500 Received: by py-out-1112.google.com with SMTP id u77so5459270pyb.16 for ; Mon, 17 Mar 2008 05:20:55 -0700 (PDT) Received: by 10.65.219.20 with SMTP id w20mr256665qbq.0.1205756454994; Mon, 17 Mar 2008 05:20:54 -0700 (PDT) Received: from ?192.168.1.110? ( [72.138.241.182]) by mx.google.com with ESMTPS id f17sm19349959qba.35.2008.03.17.05.20.54 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 17 Mar 2008 05:20:54 -0700 (PDT) Cc: Dmitry Stogov , Marcus Boerger , Andi Gutmans , Stas Malyshev , phpxcache , internals@lists.php.net Message-ID: To: Derick Rethans In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v919.2) Date: Mon, 17 Mar 2008 08:20:53 -0400 References: <06B0D32C7A96544490D18AF653D6BDE5026BA333@il-ex1.zend.net> X-Mailer: Apple Mail (2.919.2) Subject: Re: [PHP-DEV] Patch for opcode caches From: ilia@prohost.org (Ilia Alshanetsky) Keeping it seems fairly meaningless (it was a temporary hack anyway). Since 5.1 (or possibly even late 5.0) releases much of the new functionality ignores it anyway. On 14-Mar-08, at 11:23 AM, Derick Rethans wrote: > On Fri, 14 Mar 2008, Dmitry Stogov wrote: > >> however in >> PHP_5_3 we even keep ze1_compatibility_mode. >> I'm not able to remove it. > > WHy not? It's quite broken anyway. > > Derick > > -- > Derick Rethans > http://derickrethans.nl | http://ezcomponents.org | http://xdebug.org > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > Ilia Alshanetsky