Re: date() behaviour changed in 5.1?
| From: | Sean Coates | Date: | Tue, 15 Nov 2005 17:18:38 +0000 |
| Subject: | Re: date() behaviour changed in 5.1? | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-20012@lists.php.net to get a copy of this message | ||
Pierre wrote:
> On Tue, 15 Nov 2005 18:59:32 +0200 (EET)
> sniper@iki.fi (Jani Taskinen) wrote:
>
>
>> If you pass bad data to a function, it should not warn you?
>> I'd rather have it as a FATAL error. :)
>>
>> Nothing to fix here, move along. (and fix your code..)
>
>
> PHP is losely typed, I see nothing wrong to pass an integer as string
> there (for example, imagecreate("100", "100"); works).
FWIW, I don't mind forcing an INT here (or an all-numeric string) -- I
know my code was wrong; I admitted this in the first mail.
We need to warn users about it, if we do, though.
I'm only bringing this up because the behaviour _changed_ from 5.0
S