Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:39142
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error)
Cc: Greg Beaver <greg@chiaraquartet.net>,
 PHP Developers Mailing List <internals@lists.php.net>,
 Dmitry Stogov <dmitry@zend.com>
Message-ID: <A63AE881-3D54-47E1-ABC1-5596C62DE3C2@pooteeweet.org>
To: Stanislav Malyshev <stas@zend.com>
In-Reply-To: <487F8984.8030309@zend.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Mon, 21 Jul 2008 21:53:17 +0200
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> <487F8984.8030309@zend.com>
Subject: Re: [PHP-DEV] Re: towards a 5.3 release
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 17.07.2008, at 20:03, Stanislav Malyshev wrote:

> 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.

For this issue it seems like there is nobody that has enough "inertia"  
to change the current status quo. As such it seems to me like we  
should go to alpha1 as is. I hope that namespaces have enough buzz  
that we quickly get feedback after alpha1. We should do as much  
encouragement to get people to test namespaces as possible.

At the moment namespaces is probably the feature that makes me most  
nervous. Followed by GC and the re2c change.

regards,
Lukas Kahwe Smith
mls@pooteeweet.org