Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:55964 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 13586 invoked from network); 26 Oct 2011 17:12:21 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Oct 2011 17:12:21 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.163 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.163 smtp163.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.163] ([67.192.241.163:51468] helo=smtp163.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id B4/90-06370-47F38AE4 for ; Wed, 26 Oct 2011 13:12:21 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id AED963C81CB; Wed, 26 Oct 2011 13:12:17 -0400 (EDT) X-Virus-Scanned: OK Received: by smtp6.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 5E8393C81C3; Wed, 26 Oct 2011 13:12:17 -0400 (EDT) Message-ID: <4EA83F70.30601@sugarcrm.com> Date: Wed, 26 Oct 2011 10:12:16 -0700 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Daniel Convissor CC: PHP Internals List References: <20111025150637.GA8964@panix.com> In-Reply-To: <20111025150637.GA8964@panix.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [VOTE] DateTime and Daylight Saving Time Transitions From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Please take a moment to review the DateTime transitions RFC and vote on > it. I encourage voting on it to ensure we are all on the same page as > to how PHP will handle transitions. Voting is open through 10/31. Reading this RFC, I have some questions: 1. Would this ST/DST be used on format() too? If yes, then we;d get a format that nobody but PHP can parse. If no, then we don't have roundtrip for format/parse to read the same date as you wrote. 2. What is the intended use case for this syntax? I.e., if I am getting a date from somewhere, how this ST/DST is getting there? It can't come from the UI since no user and no external system would know how to generate these, and if it's supposed to be generated by the code, we get kind of chicken-and-egg problem here - to generate right ST/DST suffix, we already need to know what this date string says. So I'm a bit unclear on the use case here, especially if you're proposing to throw exceptions if the times are out of very specific hour - that means to create this suffix I'd have to know if we're in this hour or not - but how would I know that? -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227