Hi! > It confuses programmers that came from other languages, prevent APIs from > having meaningful names on static methods and have no other benefit than > supporting PHP 4 code.
I think this notion of "confuses programmers" sometimes goes too far, and this is one of the examples. PHP prides itself about having low barrier to entry, but that doesn't mean you can refuse to learn anything at all about it and PHP should change to match that. There's nothing wrong in having static and non-static functions in the same namespace, and many languages do the same. Some do not, so you should just remember PHP is the one which does. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
