Hi!
I think that's a brilliant plan. We won't ever agree on whether we want either strict type hinting, or casting typehinting and this provides both possibilities with the following pros:
For the record, I think having both is even worse than having one of them. That makes the language into mishmash of options which work similarly but different and make code harder to understand and harder to work with - imagine working with 5 libraries, 3 of which use one method and another 2 use another and you have to remember on each step which one uses which.
-- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227 -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
