Hi! > That's in a namespace, so it's not actually Integer, but > Zend\Db\Metadata\Type\Integer
Right, but it doesn't matter - in the same namespace (and in ones with suitable imports), foo(Integer $bar) still means the class, not the primitive type, and that would be broken by this RFC. Also, if integer becomes reserved word, you won't be able to write "class Integer" anymore, regardless of the namespace. > With namespaces (as in your above examples), this is already moot. I'm sorry, I don't see how this is moot if we still have the breakage as described above. > I think it's perfectly acceptable that PHP makes a built-in type a > reserved word. I would certainly not change it to PHPInt to "avoid any > obvious clashes". As I already pointed out, if we make it reserved word we'll have BC problem. We already had this experience when goto became reserved word - it resulted in a lot of breakage. This would be bigger, since we adding more reserved words and we know they are used in a lot of class names (and, possibly, method names too). -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
