Re: Why is mktime(0,0,0,0,0,0) E_STRICT?
| From: | Pierre | Date: | Mon, 23 Oct 2006 10:58:26 +0000 |
| Subject: | Re: Why is mktime(0,0,0,0,0,0) E_STRICT? | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26180@lists.php.net to get a copy of this message | ||
Hello,
On 10/23/06, Derick Rethans <derick@php.net> wrote:
On Mon, 23 Oct 2006, Pierre wrote: On 10/23/06, Derick Rethans <derick@php.net> wrote:Excuse me, can you explain what you mean? I explain you how the code you wrote works and how easy it is to fix it. A simple search clearly shows that a lot of applications use these two functions without arguments and you keep ignore this fact. Anyway, Derick's law applies again here. I really don't care, I only tried to provide a valid explanation and solution to a valid problem. Things that you, maintainer of this extension, is not able to provide. --PierreYeah, but there is no point in calling mktime() without arguments as you can use time() doing the same. It's just a friendly hint that you're wasting CPU cycles. It's an E_STRICT message for ****s sake.There is no point to keep this message, the fix is easy and does not bring any additional troubles. A lot of applications use mktime() without arguements, I did not read or hear any valid reason to do not fix this issue. Stop whining about every code I contribute. It's staying.