Re: Why 5.2 should not be delayed for E_DEPRECATED

Marcus Boerger wrote:

Liskov applies to static methods as soon as calls via objects are common which is true for PHP.

This is common in PHP and you consider this good practice? Interesting, wasn't what I would have expected...

Now given Liskov rules you can as well add default parameter values as add new parameters with default values

...

In PHP it might work as expected but then all programmers that come from langiages like C++ get confused.

I didn't realized how big an impact C++ has on the PHP design. Allow me to *shudder*, I'm glad we're only talking E_STRICT here (-:C

However the point of adding E_DEPRECATED is still open. Where open only means which version will first have it. From my perspective that will be either 5.3.0 or 6.0.0 depending on whetever comes out first. Helping here would be greatly appreciated.

What help is needed, compiling the list of E_NOTICE/E_STRICT to be convert to E_DEPRECATED? Or giving input on how to convert the individual messages? I'm willing to help. Regards, - Chris