Nope. The final decision was to only check this during E_STRICT because there's no reason why inheritance should be different from implementation. People here felt that due to PHP not supporting function overloading we should not be very strict, and therefore, only give this warning in E_STRICT.
I don't want to reopen this decision because as you can see in the archives, it was a long thread :)
Absolutely, agree about re-opening. Ok -- just wanted to check & make sure I understood (so that code wouldn't break again, etc.). This makes sense to me; early on I was one of the people (maybe the only one, actually) saying that extending interfaces should be allowed to override signatures. While many people wanted to stone me for that heresy, it's the same principle -- that because PHP doesn't support overloading things like that are necessary.
Thanks, Hans
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
