Hi! > You are completely ignoring the fact that the deprecation and removal of > gettype() is actually part of my proposal. Anyone who continues to use > gettype() should be informed that this is not the idiomatic way of > performing this action and to use the new function instead.
That makes it much worse, not better. Having two functions is bad. Having to pass through heaps of old of code, change it, re-test it, re-release it, re-deploy it, all because a basic engine function is being removed - and not because it didn't work for you, but because somebody didn't like NULL being in uppercase - is much, much worse than just having the annoyance of two similar functions. Having two functions would be bad, but tolerable - adding this huge disruption for no reason but slightly changing the output is completely unacceptable. > It might be a /slight inconsistency/ but it is at the same time a very > shameful and sad one. Our language is not able to tell us the type of a > variable! I don't know which language you are talking about, but it's certainly not PHP. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
