Hi! > The old function is actively causing confusion - the reported type-names > aren't even inconsistent with scalar type-hints, and then you have to go > and read the manual with some explanation about historical reasons why > the function doesn't work like you'd expect.
Why it should match scalar types? You can't use output of this function in a scalar type in any way. > PHP is infamous for these surprise moments. So let's add more of it by having multiple functions that do exactly the same thing but name null and float differently. > I think that gettype() should be deprecated in favor of a new function > that actually makes sense. If you think people would want to edit gigabytes of existing code because you want NULL to be lowercase, you are very seriously mistaken about the order of priority of an average PHP developer. I am sure 99.9999% of people care about all this pedantry infinitely less than they care about their code keeping working and their development not be impeded by things like having to read the manual each time to choose which two of almost identical functions they need now and which of them has null in which case. > I think that deprecating and fixing things is long-term less confusing > than documenting your way around legacy functions that produce > surprising and confusing results. I think constantly disrupting the language environment by pedantic tweaks that add BC and cognitive load but do not actually enable anything new, just move things around - is not only confusing, but harmful for the whole ecosystem. And if "NULL" really confuses you to the point you have no idea what it means - well, really, I don't know what to say. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
