Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:66479 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93613 invoked from network); 5 Mar 2013 20:59:49 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 5 Mar 2013 20:59:49 -0000 Authentication-Results: pb1.pair.com smtp.mail=steve@mrclay.org; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=steve@mrclay.org; sender-id=unknown Received-SPF: error (pb1.pair.com: domain mrclay.org from 50.22.11.19 cause and error) X-PHP-List-Original-Sender: steve@mrclay.org X-Host-Fingerprint: 50.22.11.19 bedford.accountservergroup.com Received: from [50.22.11.19] ([50.22.11.19:42614] helo=bedford.accountservergroup.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id E9/30-26085-4CC56315 for ; Tue, 05 Mar 2013 15:59:48 -0500 Received: from n128-227-117-231.xlate.ufl.edu ([128.227.117.231]:59309 helo=Distance-Ed-Sclay.local) by bedford.accountservergroup.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.80) (envelope-from ) id 1UCyxc-0006Im-Tr for internals@lists.php.net; Tue, 05 Mar 2013 14:59:45 -0600 Message-ID: <51365CBF.20101@mrclay.org> Date: Tue, 05 Mar 2013 15:59:43 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: PHP Internals References: <5122F37F.2030706@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bedford.accountservergroup.com X-AntiAbuse: Original Domain - lists.php.net X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - mrclay.org Subject: Re: [PHP-DEV] Getting separate outputs with Date Functions From: steve@mrclay.org (Steve Clay) On Wed, Feb 20, 2013 at 1:54 PM, David Soria Parra wrote: >> I ran into this myself and I personally consider date() assuming your configured TZ A >> bug. The description for date() says "local time/date" => considering TZ is not a bug. >> Timestamps are defined as UTC and the behaviour of DateTime is correct there, that it >> always assume UTC. date() should do the same. I rather think DateTime::__construct/date_create were wrongly designed for ignoring the second parameter. Timestamps specify a uniform reference of time, but just because you use them doesn't imply you're sitting in any particular TZ. Steve Clay -- http://www.mrclay.org/