Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40349
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 <cellog@php.net>,
 PHP Developers Mailing List <internals@lists.php.net>,
 Dmitry Stogov <dmitry@zend.com>
Message-ID: <A077B6EC-3E30-4F46-91CA-FD75D578CC7A@pooteeweet.org>
To: Stanislav Malyshev <stas@zend.com>
In-Reply-To: <48C55855.4080602@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, 8 Sep 2008 19:00:05 +0200
References: <ADD0525F-F900-4F3A-9B76-1ED332CA31E0@pooteeweet.org> <486FA5FB.1000300@php.net> <E06A1FB3-971F-4D4F-850A-D0255F7275F7@pooteeweet.org> <48C55855.4080602@zend.com>
Subject: Re: towards a 5.3 release
From: mls@pooteeweet.org (Lukas Kahwe Smith)


On 08.09.2008, at 18:52, Stanislav Malyshev wrote:

> Hi!
>
>> I think given the feedback from users, we really need to actually  
>> benchmark the performance slow down that Greg's proposed changes  
>> will bring. I also guess there are two types of users out there:
>
> Could you summarize the feedback?

I am mainly baseing myself on the feedback I got at:
http://pooteeweet.org/blog/1288

However I also got some feedback from others on IRC that all went in  
the same direction.

I think Liz summarized the gripes best (especially the second  
paragraph is important to note):
"I've been using namespaces since then went into 5.3. From my  
experience functions in namespaces are basically unusable (you can't  
alias in a function like you can a class from a namespace - plus  
there's the ambiguity issue with static methods).

Writing HUGE blocks of use statements at the top is going to turn  
people off and since included files have their own namespace level you  
can't even have a file that keeps a block of use statements that are  
needed on every page.

Since I do more than just web applications with PHP, I HAVE run into  
the need to get away from the "one namespace per file" rule, and the  
fact that you can't have ANYTHING before the opening <?php tag in a  
file with a namespace (no whitespace, no html, nothing) without a  
fatal error annoys me to no end."

Chuck adds:
"I think that user-level classes are far more common in PHP than  
internal classes, and as such should be given priority."

regards,
Lukas Kahwe Smith
mls@pooteeweet.org