Re: 6.0 And Moving Forward

On Tue, Jul 17, 2012 at 8:48 AM, Dan Cryer <dan@dancryer.com> wrote: > > > > The problem, of course, is changing and removing things can break BC. I'd > > love to remove list() too, but that would break code relying on it. > > > Isn't that kind of the point of the whole discussion? This is talking about > completely rewriting the standard library for PHP 6, but providing a legacy > extension/compile time option, which would bring with it almost complete > backwards compatibility with PHP 5. > > I think any reasonable person would expect there to be a significant number of BC breaks in any major version increment. That being said, wouldn't it be possible in most of these cases to just do what we already do and use the E_DEPRECATED flag? That way, people will have a reasonable amount of time to update their code to current standards before a behavior is removed completely. And in cases where E_DEPRECATED