Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:26158 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 27285 invoked by uid 1010); 22 Oct 2006 22:05:28 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 27269 invoked from network); 22 Oct 2006 22:05:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Oct 2006 22:05:28 -0000 Authentication-Results: pb1.pair.com smtp.mail=iliaal@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=iliaal@gmail.com; sender-id=pass; domainkeys=good Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.162.193 as permitted sender) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: iliaal@gmail.com X-Host-Fingerprint: 64.233.162.193 nz-out-0102.google.com Linux 2.4/2.6 Received: from [64.233.162.193] ([64.233.162.193:31349] helo=nz-out-0102.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 17/B9-54754-52BEB354 for ; Sun, 22 Oct 2006 18:05:27 -0400 Received: by nz-out-0102.google.com with SMTP id o1so591105nzf for ; Sun, 22 Oct 2006 15:05:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=OFMkRPBVHP9Hn45+nuqNy67x6oYtfw2fFJwr1viWGbPvkl15Tp3BanAhcD8OfxfM7ZhVm2JL2GDctr6J0YXtWssZBqINxGrs+ZBYv0fosBo8hjUsN0FW6/3FUSnflNWctoSgYKmq54uyIoEhcEotlmwSpUzZ6izGhKgStmlyx7g= Received: by 10.65.84.6 with SMTP id m6mr4227681qbl; Sun, 22 Oct 2006 15:05:23 -0700 (PDT) Received: from ?192.168.1.6? ( [74.108.69.82]) by mx.google.com with ESMTP id e19sm4869512qbe.2006.10.22.15.05.22; Sun, 22 Oct 2006 15:05:22 -0700 (PDT) In-Reply-To: <10845a340610221045x2439b02alee7829425c902468@mail.gmail.com> References: <10845a340610221045x2439b02alee7829425c902468@mail.gmail.com> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-ID: <1B060546-A982-497C-8241-680044CDED15@prohost.org> Cc: "php internals LIST" Content-Transfer-Encoding: 7bit Date: Sun, 22 Oct 2006 18:05:15 -0400 To: RQuadling@GoogleMail.com X-Mailer: Apple Mail (2.752.3) Sender: Ilia Alshanetsky Subject: Re: [PHP-DEV] Why is mktime(0,0,0,0,0,0) E_STRICT? From: ilia@prohost.org (Ilia Alshanetsky) Use of mktime(0) and alike is improper use of the function, more over generally it can be traced to an undesired code behavior. On 22-Oct-06, at 1:45 PM, 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? > > -- > ----- > Richard Quadling > Zend Certified Engineer : http://zend.com/zce.php? > c=ZEND002498&r=213474731 > "Standing on the shoulders of some very clever giants!" > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > Ilia Alshanetsky