Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:26166
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain php.net from 82.94.239.5 cause and error)
Date: Mon, 23 Oct 2006 08:56:18 +0200 (CEST)
To: Ilia Alshanetsky <ilia@prohost.org>
cc: Rasmus Lerdorf <rasmus@lerdorf.com>, Lukas Kahwe Smith <lsmith@php.net>,
        Richard Quadling <rquadling@googlemail.com>,
        php internals LIST <internals@lists.php.net>
In-Reply-To: <3A2844B2-C513-47C9-9B62-02DE97447618@prohost.org>
Message-ID: <Pine.LNX.4.62.0610230855390.3561@localhost>
References: <10845a340610221045x2439b02alee7829425c902468@mail.gmail.com>
 <Pine.LNX.4.62.0610222315490.3561@localhost> <453BE73B.4020300@php.net>
 <59BCAFC2-C867-47B8-82D3-1BD0887568FE@prohost.org> <453BF05D.9070006@lerdorf.com>
 <3A2844B2-C513-47C9-9B62-02DE97447618@prohost.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] Why is mktime(0,0,0,0,0,0) E_STRICT?
From: derick@php.net (Derick Rethans)

On Sun, 22 Oct 2006, Ilia Alshanetsky wrote:

> 
> On 22-Oct-06, at 6:27 PM, Rasmus Lerdorf wrote:
> > Yes, but E_STRICT is not an argument validation error level.  Throwing an
> > E_STRICT here is quite wrong unless we have completely redefined E_STRICT to
> > mean just about any sort of error.  mktime($a) is perfectly fine at the
> > language level and E_STRICT is supposed to be language-level errors not
> > something that is thrown based on the value of $a.
> 
> As Pierre had correctly identified the E_STRICT currently is only raised in 2
> instance mktime() <-- no args or when the deprecated dst parameter is being
> used. While I agree that E_STRICT maybe misused there, it is only the case if
> the decision is to maintain the mktime() == time() functionality.

And I'd be happy to change both to E_DEPRECATED when we get that error 
level.

regards,
Derick