Re: Why is mktime(0,0,0,0,0,0) E_STRICT?

From: Date: Sun, 22 Oct 2006 22:44:12 +0000
Subject: Re: Why is mktime(0,0,0,0,0,0) E_STRICT?
References: 1 2 3 4 5  Groups: php.internals 
Request: Send a blank email to internals+get-26163@lists.php.net to get a copy of this message
On 22-Oct-06, at 6:27 PM, Rasmus Lerdorf wrote:
Yes, but E_STRICT is not an argument validation error level. Throwing an E_STRICT here is quite wrong unless we have completely redefined E_STRICT to mean just about any sort of error. mktime($a) is perfectly fine at the language level and E_STRICT is supposed to be language-level errors not something that is thrown based on the value of $a.
As Pierre had correctly identified the E_STRICT currently is only raised in 2 instance mktime() <-- no args or when the deprecated dst parameter is being used. While I agree that E_STRICT maybe misused there, it is only the case if the decision is to maintain the mktime() == time() functionality. Ilia Alshanetsky

« previous php.internals (#26163) next »