> On 10 Oct 2008, at 06:03, Lukas Kahwe Smith wrote:
>
> 1) rip them out
>
> I'm +1 on this. We simply don't have consensus, and I don't see anyway
> we
> can have consensus by the time 5.3 has to be frozen. Once namespaces
> are in,
> we're gonna have to stick with whatever we choose, unless we totally
> break
> BC.
I'd agree with this, leave something with such a big impact to version 6.
At
least it gives time to get it right.
I don't agree to this, many of us are waiting for namespaces and have
starting to impact some code in prevision.
Don't forget that an annoucement has been done on php.net and a final
release of 5.3 without namespaces could be interpreded as a regression.
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. 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. Leaving as-is, we already know is problematic. There's no consensus
to pull support for functions/constants, which would make it less
problematic.
'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.
- Steph
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
