Derick's point was about consistency. The approach described in his mail is consistent with current syntax and mechanism(s). Current typehints do not apply any kind of conversion, so treating scalar hints the same way is consistent with the current mechanism.
Reusing the typecasting syntax for typecasting "hints" makes them more familiar to the users, and it is less ambiguous than a typehint that sometimes also typecasts. Plus, it allows for both "strict" typechecking and the more relaxed typecasting thing instead of forcing one. And all of that with a syntax that feels familiar. That, I believe, was his point. -JD -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
