Re: Why is mktime(0,0,0,0,0,0) E_STRICT?
| From: | Ilia Alshanetsky | Date: | Mon, 23 Oct 2006 15:37:05 +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 11 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-26186@lists.php.net to get a copy of this message | ||
Unilateral break? lol...
Actually it is no break at all, take PHP4 code move it to PHP and you won't even see the warning because E_STRICT is not even shown by default.
On 23-Oct-06, at 11:26 AM, Pierre wrote:
Hello, On 10/23/06, Ilia Alshanetsky <ilia@prohost.org> wrote:Ilia AlshanetskyOn 23-Oct-06, at 6:41 AM, Pierre wrote:If you read the other replies to your initial question (which was wrong :), you will realize another thing, this is easily fixablewithminimum effort and impact: http://pecl.php.net/~pierre/remove_mktime_strict.txt No visible speed differenceI see no reason to make mktime() an alias of time(), you are basically advocating misuse of functions. Yes there are over 2,000 results on google showing people calling mktime(), but I bet there are even more register_globals users and yet we've all decided to remove it in PHP6.Ilia, it is not about making an alias. It is about restoring a widely use behavior in mktime and about making gmktime useable. This change is nothing but a unilateral break (even in E_STRICT). --PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php