Hi! > OK. In my opinion, if something is defined as "int" should be always > "int". Nor "null" neither "undefined". > This is good for programmers who think like me, for compiler and for > hardware CPU :)
I understand why it's good, and I agree. The harder question is whether we can deliver on that, and whether we can deliver on that without introducing limitations that do not make semantic sense. unset is just the start of it, initialization/unserialization/etc. issues are part of it too. > You have another opinion, and we won't persuade each other. I think you slightly misunderstand my opinion - I don't say "always int, never undefined" is not good, I say it might be good in theory but it looks practically impossible, we should prepare for the other possibility. Of course, it may be that I am completely wrong and it is practically possible, in which case - once that practicality is proven - I would agree with you. That would be the way to persuade me :) -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
