Newsgroups: php.internals,php.internals Path: news.php.net Xref: news.php.net php.internals:26152 php.internals:26157 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 74939 invoked by uid 1010); 22 Oct 2006 17:45:17 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 74923 invoked from network); 22 Oct 2006 17:45:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Oct 2006 17:45:17 -0000 Authentication-Results: pb1.pair.com smtp.mail=rquadling@googlemail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=rquadling@googlemail.com; sender-id=pass; domainkeys=good Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 64.233.166.183 as permitted sender) DomainKey-Status: good X-DomainKeys: Ecelerity dk_validate implementing draft-delany-domainkeys-base-01 X-PHP-List-Original-Sender: rquadling@googlemail.com X-Host-Fingerprint: 64.233.166.183 py-out-1112.google.com Linux 2.4/2.6 Received: from [64.233.166.183] ([64.233.166.183:9092] helo=py-out-1112.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id CB/03-54754-A2EAB354 for ; Sun, 22 Oct 2006 13:45:15 -0400 Received: by py-out-1112.google.com with SMTP id t32so210361pyc for ; Sun, 22 Oct 2006 10:45:11 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=googlemail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=BfoqHMCP//3MnDO48JmB4MJu152p5DreBGVsvAaLuTNyBF6+TQw44MOPLVMbkm6G6GVgesM77MNhzRRMGVsAWRT445lnFDigP0IxFJgYTQX8kYui4+i69+rChMpjRQ8Ku4jMyrwPf3ndG/kAuXAyAUP/iOn/KjlIQHY92cUYKeI= Received: by 10.35.97.1 with SMTP id z1mr5003519pyl; Sun, 22 Oct 2006 10:45:11 -0700 (PDT) Received: by 10.35.97.14 with HTTP; Sun, 22 Oct 2006 10:45:11 -0700 (PDT) Message-ID: <10845a340610221045x2439b02alee7829425c902468@mail.gmail.com> Date: Sun, 22 Oct 2006 18:45:11 +0100 Reply-To: RQuadling@GoogleMail.com To: "php internals LIST" MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [PHP-DEV] Why is mktime(0,0,0,0,0,0) E_STRICT? From: rquadling@googlemail.com ("Richard Quadling") 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!"