Re: Why is mktime(0,0,0,0,0,0) E_STRICT?
| From: | Lukas Kahwe Smith | Date: | Sun, 22 Oct 2006 21:48:43 +0000 |
| Subject: | Re: Why is mktime(0,0,0,0,0,0) E_STRICT? | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26156@lists.php.net to get a copy of this message | ||
Derick Rethans wrote:
On Sun, 22 Oct 2006, Richard Quadling wrote:as I just said on IRC: i think an e_strict in that place is wrong .. for example the parameters could have been user supplied and you simply check that the parameters are integers if e_strict is our way of telling users about back practices, we should really have a consensus on this list about what constitutes a bad practice. regards, LukasWith the recent discussion on E_STRICT and the waste of cpu cycles ... Why is mktime(0, 0, 0, 0, 0, 0) generating E_STRICT? What is unstrict about this? Why is important to use time() instead?It's quicker.