On Fri, May 15, 2009 at 1:25 PM, Lukas Kahwe Smith <m...@pooteeweet.org> wrote:
> Confusing new code is totally different from breaking existing code. True but aren't some changes in 6.0 at least (and possibly 5.3) going to require code changes? Or is it still going to be "legacy enough" ? There's gotta be a time in the natural evolution to "cut the cord" so to speak - Python just launched 3.0 and dropped backwards compatibility. Why can't PHP do the same in 6.0? :) (Or 5.3 for all I care. But it really should align with a major revision #) > Just FYI: Not sure which blog you are talking about, but that is Stefan > Esser's blog that is linked above. Sorry, used to most people pushing their own blog links :) -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
