> Yes, the database use case and exterior data has been my main concern over > the type hint proposals. Now, this could also be changed (fixed, etc) on > a > different layer (aka database extensions to deal with native types) but > that is > likely far more to bite off than one would want at this point. It is > relatively > painless to go in and cast all of those types but the amount of code out > there > which people are going to just 'expect' this to work will be fairly large > and > one of those cases that will possibly be cause for migration concerns.
Thanks a lot for the input! We'll reconsider accepting "1"/"0" as valid Booleans as the original proposal did. Zeev -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
