Hi! >> Hmm. Well, if we're doing mass deprecations, maybe we should finally get rid >> of
I must note that I think this drive to "get rid of" functions that does not stand in anybody's way (as opposed to the case of __autoload which is incompatible with superior stackable autoloader solution) is deeply misguided. Yes, there are functions that are very niche and maybe not a lot of people use them. But the advantage of PHP was always to try and serve a lot of needs and be a versatile pragmatic instrument, even at the expense of theoretical purity. I do not think we should abandon this approach. If there is a conceivable use case where this function can be useful, and it does not impede progress or prevent implementation of better features - IMO there's no reason at all to remove it. It's better to have a hundred of functions and have 10 year old code running perfectly in modern version than to have new squeaky clean API than has no code to run because 100% of existing code can not use this version (and thus even if people wanted to use clean API in new code they can't because old one does not work). -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
