Hi! > It was always an E_STRICT error to call a non-static method statically > (as usual, not counting scoped calls) and since PHP 5.6 it was > E_DEPRECATED in the most common case. I don't see why we would suddenly > want to go back on this and make it work without any warnings.
The reason why is simple - it works, it doesn't produce any bad behavior, it's clear what it does, so why produce warnings that are essentially useless to the user as they don't warn them about any potential problem? Unless, of course, I'm missing some potential problem - please point it out then. But "we've always done it this way" is not particularly good argument in this case - we did many things one way and then changed and started doing it a better way. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
