Re: date() behaviour changed in 5.1?

Hello Rasmus, to have this idea posted a second time. I think we should have all native types be auto converted and add a flag for the _ex version of the parsing api that prevents from auto conversion. However we are to close to release so i think we should do that only in 5.1.1 (ilia most probably doesn't want to have rc6?). regards marcus Wednesday, November 16, 2005, 10:46:23 AM, you wrote: > Jakub Vrana wrote: >> Rasmus Lerdorf wrote: >>> 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. >> >> I want be warned about wrong parameters. I (as a doc-guy) would rather >> describe strict and non-strict casting than not be warned about >> obviously wrong wordwrap("abc", "b"). >> >> I naturally agree with consistent parsing of parameters through >> zend_parse_parameters() - my script checking if parameters in source >> and documentation match uses it. > Right now, without looking at the source code, there is no way to tell > which functions do strict casting and which ones don't. > -R Best regards, Marcus