Re: Why is mktime(0,0,0,0,0,0) E_STRICT?
| From: | Derick Rethans | Date: | Mon, 23 Oct 2006 10:48:58 +0000 |
| Subject: | Re: Why is mktime(0,0,0,0,0,0) E_STRICT? | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26179@lists.php.net to get a copy of this message | ||
On Mon, 23 Oct 2006, Pierre wrote:
> On 10/23/06, Derick Rethans <derick@php.net> wrote:
>
> > Yeah, 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.
Derick