Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:40484 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25619 invoked from network); 12 Sep 2008 19:23:36 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Sep 2008 19:23:36 -0000 Authentication-Results: pb1.pair.com header.from=stas@zend.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=stas@zend.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.163 as permitted sender) X-PHP-List-Original-Sender: stas@zend.com X-Host-Fingerprint: 212.25.124.163 il-gw1.zend.com Windows 2000 SP4, XP SP1 Received: from [212.25.124.163] ([212.25.124.163:44362] helo=il-gw1.zend.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A2/47-22777-6B1CAC84 for ; Fri, 12 Sep 2008 15:23:35 -0400 Received: from us-ex1.zend.com ([192.168.16.5]) by il-gw1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Sep 2008 22:24:46 +0300 Received: from [192.168.16.110] ([192.168.16.110]) by us-ex1.zend.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 12 Sep 2008 12:24:32 -0700 Message-ID: <48CAC1EF.2090501@zend.com> Date: Fri, 12 Sep 2008 12:24:31 -0700 Organization: Zend Technologies User-Agent: Thunderbird 2.0.0.16 (Windows/20080708) MIME-Version: 1.0 To: Gregory Beaver CC: internals@lists.php.net References: <48C59D5C.4050507@chiaraquartet.net> <48C5A909.4030502@zend.com> <48C602D5.6020704@chiaraquartet.net> <48C6A6AA.7050003@zend.com> <48C9F2F6.4080007@chiaraquartet.net> In-Reply-To: <48C9F2F6.4080007@chiaraquartet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Sep 2008 19:24:32.0328 (UTC) FILETIME=[2EF42480:01C9150D] Subject: Re: [PATCH] Re: [PHP-DEV] namespace examples (solving name resolutionorder issues) From: stas@zend.com (Stanislav Malyshev) Hi! > The caching is at runtime. Basically, it's in executor_globals, and so > is not linked to any opcode array (I couldn't figure out any other > globally accessible storage location). It works like an associative > array. If file X.php loads XMLReader in namespace namespacename, it > creates this entry: > > array( > 'X.php\0namespacename::XMLReader' => {class entry for XMLReader} > ); I though a bit about that patch, and I see following problems with it: 1. If you do not use autoloading, you still can get different resolution, e.g.: