Hi!
*We* don't force anybody. API developers *could potentionally* force their consumers to take care about their types.
Which is IMO bad idea. Having dynamic language means you care about the data, but not its internal representation. Now you are stepping back and telling them "you need not only to watch your data - you need at each moment to know how exactly PHP keeps it, what type each zval carries at each moment - in case it ever gets passed to strictly-typed function." It is not enough anymore that you are sure some item holds some flags that can be zero or not - you'd have to ensure it gets "boolean type" bit or your function is going to reject it. So we get all annoyances of a strictly typed language - without the added safety of the compiled strictly typed language. IMO, it's a bad deal.
-- 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
