Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39064
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 212.25.124.163 as permitted sender)
Message-ID: <487F8984.8030309@zend.com>
Date: Thu, 17 Jul 2008 11:03:48 -0700
Organization: Zend Technologies
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
To: Lukas Kahwe Smith <mls@pooteeweet.org>
CC: Greg Beaver <greg@chiaraquartet.net>, 
 PHP Developers Mailing List <internals@lists.php.net>,
 Dmitry Stogov <dmitry@zend.com>
References: <ADD0525F-F900-4F3A-9B76-1ED332CA31E0@pooteeweet.org> <486FA5FB.1000300@php.net> <4872B5D4.1000205@zend.com> <4877CE04.4070104@chiaraquartet.net> <D3AC2DC2-23E4-4823-AFB6-0FDB74DD896D@pooteeweet.org>
In-Reply-To: <D3AC2DC2-23E4-4823-AFB6-0FDB74DD896D@pooteeweet.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: towards a 5.3 release
From: stas@zend.com (Stanislav Malyshev)

Hi!

> Greg's argument seems sound to me. With the proposed change errors are 
> less likely and more transparent in case they happen (for people using 

No, they won't be transparent at all. If you use Exception and forget to 
put "use ::Exception" in each and every of your files, you get 
exhaustive search of include path (not helped by bytecode caching, btw - 
all bytecode caches I know cache existing files, not searches for 
non-existing ones) on each mention of Exception. You can not see it - on 
the surface, everything works fine. Then, when you think your code is 
fine, you run profiler and boom - you see 200 file accesses where there 
should be none.

> autoload that is). At the same time people who care about performance 
> can still work around this behavior (then again those that care about 
> optimizations on this level probably do not use autload to begin with).

What's wrong with autoload? You sound like autoload is somehow contrary 
to performance, which is not true.

> So I guess the point is .. autoload is there for convinience, so lets 
> make it as convinient as possible.

I don't see how having internal class mention trigger exhaustive 
autoload search is "as convenient as possible". For me, it is a huge 
landmine under every PHP application trying to use namespaces - forget 
one use statement and boom, your performance is gone. If you want to do 
that, you better force using ::Class everywhere - this way at least 
there's a way to know where it will blow up without running system call 
traces on every piece of code.
-- 
Stanislav Malyshev, Zend Software Architect
stas@zend.com   http://www.zend.com/
(408)253-8829   MSN: stas@zend.com