Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:41002 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 92571 invoked from network); 14 Oct 2008 17:51:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Oct 2008 17:51:25 -0000 Authentication-Results: pb1.pair.com header.from=office@kitsoftware.ro; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=office@kitsoftware.ro; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain kitsoftware.ro from 81.196.12.70 cause and error) X-PHP-List-Original-Sender: office@kitsoftware.ro X-Host-Fingerprint: 81.196.12.70 smtp1.rdslink.ro Linux 2.4/2.6 Received: from [81.196.12.70] ([81.196.12.70:51246] helo=smtp.rdslink.ro) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FC/CC-25867-A1CD4F84 for ; Tue, 14 Oct 2008 13:51:24 -0400 Received: (qmail 3089 invoked from network); 14 Oct 2008 17:51:20 -0000 X-Mail-Scanner: Scanned by qSheff 1.0 (http://www.enderunix.org/qsheff/) Received: from unknown (HELO CZA) (86.121.162.70) by smtp1.rdslink.ro with SMTP; 14 Oct 2008 17:51:19 -0000 To: "'Steph Fox'" , "'Stanislav Malyshev'" , References: <652122.8719.qm@web708.biz.mail.mud.yahoo.com> <48F4D832.7010708@zend.com> <033701c92e24$d9ca3d60$3ffc1f3e@foxbox> In-Reply-To: <033701c92e24$d9ca3d60$3ffc1f3e@foxbox> Date: Tue, 14 Oct 2008 20:51:10 +0300 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0009_01C92E3E.96BEB360" X-Priority: 1 (Highest) X-MSMail-Priority: High X-Mailer: Microsoft Office Outlook 12.0 Importance: High Thread-Index: AckuJK6dKzBva181QH6HjsgZWMO8EgAAFBfA Expiry-Date: Thu, 13 Nov 2008 01:00:00 +0300 Content-Language: en-us Disposition-Notification-To: "Catalin Zamfir Alexandru | KIT Software CAZ" Subject: RE: [PHP-DEV] namespaces and alpha3 From: office@kitsoftware.ro ("Catalin Zamfir Alexandru | KIT Software CAZ") ------=_NextPart_000_0009_01C92E3E.96BEB360 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Guys, a recomandation (about namespaces): - if it's not tested enough, don't include it in the release. - if it's going to make a lot of confusion, don't include it in the release. - if neither of the two above won't stop it being included, and if there aren't 3 quarters (75%) of developers willing to accept namespaces, don't include it in the release. - in short, whatever feature that may cause more headaches or doesn't have any real support in the developer community should not be packed for a release. Those were my 2 cents ... Yours, Catalin Z. Alexandru ---------------------------- > -----Original Message----- > From: Steph Fox [mailto:steph@php.net] > Sent: Tuesday, October 14, 2008 8:47 PM > To: Stanislav Malyshev; internals@lists.php.net > Subject: Re: [PHP-DEV] namespaces and alpha3 > > Hi Stas, > > > The thing is that there's nothing here that would improve with time. > > Except the chance to test approaches that are currently only theories. > > > Pushing in to 6.0 is basically throwing it out forever, since there's > > nothing we could do in 6.0 that we can't do now, there's nothing that > we > > could do "only if we had time", and only thing will happen towards the > > release of 6.0 is that we will repeat the whole story again. > > Not so, most of it's there, agreed and tested. What there is, is already > in > PHP 6. > > I don't see > > how anything will change in 6.0 from now except that it will happen in > 2-3 > > years, > > I would _hope_ it would happen from the moment 5.3 is out of the door, > not > at the last moment before the 6.0 release! > > > so in the meantime PHP would miss a feature much needed, much > advertised > > and much supported by the user base. > > We are at the point we just need to take decision. I understand the > > natural tendency of people to avoid taking complicated decisions by > > postponing the problem, but if you are not ready to take the > > responsibility, please do not try to put is as any kind of decision. > > This was one of the four options we were given. Just because you don't > like > it, doesn't mean there are now only three. > > > It is not. If you don't know what to do with it, if you don't > understand > > the feature, if you don't feel comfortable with deciding how it should > > be - don't say "let's throw it off", it is not a constructive > approach. > > There's nothing that will change from now to 6.0 except that the > people > > who worked a lot on this feature would be less ready to repeat the > ordeal. > > This is very negative, Stas. "Everybody wants it so let's push it out > without testing". Do you really want a repeat of 5.0? > > > So please do not allow inability to take decision and unwillingness to > > address the problem to deprive PHP users of much needed functionality. > > Please don't go emotional on us :) > > - Steph > > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php ------=_NextPart_000_0009_01C92E3E.96BEB360--