Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:40997
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain tonybibbs.com from 209.191.119.233 cause and error)
Date: Tue, 14 Oct 2008 08:03:05 -0700 (PDT)
To: internals@lists.php.net
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID: <652122.8719.qm@web708.biz.mail.mud.yahoo.com>
Subject: Re: [PHP-DEV] namespaces and alpha3
From: tony@tonybibbs.com (Tony Bibbs)

This is what I've be fearing.  First slated for 5.0.  Then 5.3.  Now 6.0.  It appears there's consensus to rip it out which, in my prior post, I was all for if people felt it meant getting it right.  Apparently that is the case.  I guess my main question is what keeps this from being pushed yet again once 6.0 drops?  From the community standpoint we keep hearing "its coming, its coming" but here we are still waiting.  Again, I'm fine with the decision but I think others share similar concerns and will want to hear a commitment (dare I say promise) to adding namespaces to 6.0.

--Tony



----- Original Message ----
From: Stefan Walk <et@php.net>
To: internals@lists.php.net
Sent: Tuesday, October 14, 2008 7:46:58 AM
Subject: Re: [PHP-DEV] namespaces and alpha3

On Tuesday 14 October 2008 14:10:50 Steph Fox wrote:
> I'm +1 on ripping out and leaving til 6.0. I don't think there is enough
> time between now and the 5.3.0 code freeze to make major changes to the
> language syntax. 

Major changes like ripping the feature that most people are looking forward to 
in 5.3 out?

> Making -> do double duty and adding E_STRICT messages to 
> currently legal code really doesn't look like a good option to me, much
> less during a point release and even less during the final moments of a
> release cycle. 

That E_STRICT was proposed for 6, not for 5.3, and is not a requirement - and 
about "double duty", it's not really unintuitive to reference to "members" of 
classes the same way you reference to "members" of instances.

> 'An announcement has been done on php.net' simply isn't a good enough
> reason to screw up the language; we can write new announcements and even
> explanations. And we already have *most* of a working implementation in
> 6.0, so it's not like ripping it out of 5.3 means starting over from
> scratch.

I would love to see the public reaction to those "new announcements and 
explanations", so in a way it's a win-win situation for me.

Regards,
Stefan

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php