I thought about this a bit more, but couldn't actually see why something like "nullable" is needed at all. Simple solution: If you expect an object of a specific class; if it also might be NULL, don't use a class hint at all. So *why* do we even need "bloat" like "nullable" or something similar.
As someone who has invested many, many thousands of lines of code in PHP5, it is in my interest to have things work they way they currently work. Requiring a new keyword is a pretty big BC break to existing PHP5 releases, and while I understand that PHP5 is not stable & hence I shouldn't be complaining if you all do decide to break things (still dealing with aftermath of __toString() change) I also don't think the current implementation is all that bad.
Allowing NULL even if there is a typehint doesn't bother me personally at all :) Perhaps if it must be changed, then NULL could be allowed only for parameters that had a default type of NULL? That would be equally acceptible, and simpler than having new PHP keyword.
My $0.02,
Hans
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
