Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26156 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 24143 invoked by uid 1010); 22 Oct 2006 21:48:57 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 24128 invoked from network); 22 Oct 2006 21:48:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Oct 2006 21:48:57 -0000 Authentication-Results: pb1.pair.com header.from=lsmith@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=lsmith@php.net; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain php.net from 212.112.227.169 cause and error) X-PHP-List-Original-Sender: lsmith@php.net X-Host-Fingerprint: 212.112.227.169 ipx11223.ipxserver.de Linux 2.5 (sometimes 2.4) (4) Received: from [212.112.227.169] ([212.112.227.169:33103] helo=ipx11223.ipxserver.de) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id AA/29-54754-947EB354 for ; Sun, 22 Oct 2006 17:48:57 -0400 Received: from localhost (localhost [127.0.0.1]) by ipx11223.ipxserver.de (Postfix) with ESMTP id 72F93DF01D5; Sun, 22 Oct 2006 23:48:54 +0200 (CEST) Received: from ipx11223.ipxserver.de ([127.0.0.1]) by localhost (flottensignalgeber [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25876-07; Sun, 22 Oct 2006 23:48:52 +0200 (CEST) Received: from [127.0.0.1] (i577B7A54.versanet.de [87.123.122.84]) by ipx11223.ipxserver.de (Postfix) with ESMTP id 353B7DF0026; Sun, 22 Oct 2006 23:48:52 +0200 (CEST) Message-ID: <453BE73B.4020300@php.net> Date: Sun, 22 Oct 2006 23:48:43 +0200 User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) MIME-Version: 1.0 To: Derick Rethans Cc: Richard Quadling , php internals LIST References: <10845a340610221045x2439b02alee7829425c902468@mail.gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by somedaemon at backendmedia.com Subject: Re: [PHP-DEV] Why is mktime(0,0,0,0,0,0) E_STRICT? From: lsmith@php.net (Lukas Kahwe Smith) Derick Rethans wrote: > On Sun, 22 Oct 2006, Richard Quadling wrote: > >> With the recent discussion on E_STRICT and the waste of cpu cycles ... >> >> Why is mktime(0, 0, 0, 0, 0, 0) generating E_STRICT? >> >> What is unstrict about this? >> >> Why is important to use time() instead? > > It's quicker. as I just said on IRC: i think an e_strict in that place is wrong .. for example the parameters could have been user supplied and you simply check that the parameters are integers if e_strict is our way of telling users about back practices, we should really have a consensus on this list about what constitutes a bad practice. regards, Lukas