Hi!
I get this, really, I do, again. Like the previous post I (likely we) understand.
Unfortunately, it looks like you do not. Probably my failure to explain it clearly.
Did you not get or read my post? You say again and again 1 == '1', but you are forgetting those OTHER operators, === and !==. 1 !== '1' does it? ====>Add numeric hinting like I said 50 posts ago and your 1 == '1'
I do not talk about the bits in the engine and how all the operators work. I talk about how the user thinks (or should think) about using PHP. Yes, === exists for a reason. But, in most cases == is what you really want, that's why it got to be ==.
the API level. People who want to make it strictly integer, will
Again, people who want to make it strictly integer are wrong in 90% of the cases. Because of that, giving them more tools to be wrong in 90% of the cases is... well, wrong :) Other 10% are possible, but they do not belong to the language syntax.
continue to do so as they do now. You can not, and should not want to, control the way people program.
When you design the language, that's what you do, to some measure. You program differently in C, Prolog, LISP, Javascript or PHP. At least, you should - otherwise you are working against the grain of the language and only make yourself work harder then necessary. Of course, you want to give people more tools - but some tools just don't belong there. That's why C[++] has operator* and PHP does not.
But I know this will never happen because no one cares what users want... your logic of
You seem to confuse "what users want" with "what I want". I don't get all I want from PHP too, and sometimes I think it's wrong. But I also know it is not possible for PHP to satisfy 100% of feature requests from everybody - and even if it were, it would make PHP worse, not better. PHP is in constant process of improvement, so claiming "no one cares what users want" is just contrary to the facts.
How in the world, does this remotely, possibly, even slightly make sense?
It doesn't, because you wrote it so on purpose, to misrepresent my position. The position is simple. PHP has certain set of ideas behind it, and certain way of doing things. Having strict hints in function definitions promotes entirely different way of doing things, which fits compiled languages much better and dynamic language like PHP much worse.
-- Stanislav Malyshev, Zend Software Architect [EMAIL PROTECTED] http://www.zend.com/ (408)253-8829 MSN: [EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
