Re: Why is mktime(0,0,0,0,0,0) E_STRICT?
| From: | Pierre | Date: | Mon, 23 Oct 2006 10:46:11 +0000 |
| Subject: | Re: Why is mktime(0,0,0,0,0,0) E_STRICT? | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26178@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, Lukas Kahwe Smith wrote:How can I have "gmmktime();" (which also uses php_mktime) with time()? --PIerreI meant, there would be a BC break if this feature gets dropped, which is the point of the message, right? 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.Yes, I see no point in pushing this responsibility into the userland, especially since its a BC break appearently.There is no BC break: