Re: date() behaviour changed in 5.1?
| From: | Lukas Smith | Date: | Tue, 15 Nov 2005 20:44:11 +0000 |
| Subject: | Re: date() behaviour changed in 5.1? | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals php.internals |
| Request: | Send a blank email to internals+get-20030@lists.php.net to get a copy of this message | ||
Rasmus Lerdorf wrote:
Wez Furlong wrote:+1 this is really what i have come to expect from PHP (which is why I never understood why we changed array_merge to not cast null to an empty array back in PHP 5.0.0) regards, LukasI can't think of any case where you'd want to error out when given '100 ' if it would accept '100' quite happily. I'd lean towards a single cast semantic for this, and remove that strict checking flag from zend_parse_parameters(); lazy dynamic type handling for primitive data types is one of the cornerstones of PHP IMO.Yeah, I am leaning towards that as well. I don't like the inconsistency between direct casting via (int) vs. zend_parse_parameter's strict casting. It is much simpler to explain that functions will cast to the required parameter type and have one consistent way to cast things.