Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:67547 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 8975 invoked from network); 27 May 2013 07:20:45 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 27 May 2013 07:20:45 -0000 Authentication-Results: pb1.pair.com smtp.mail=swhitemanlistens-software@cypressintegrated.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=swhitemanlistens-software@cypressintegrated.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain cypressintegrated.com designates 173.1.104.101 as permitted sender) X-PHP-List-Original-Sender: swhitemanlistens-software@cypressintegrated.com X-Host-Fingerprint: 173.1.104.101 rproxy2-b-iv.figureone.com Windows 2000 SP2+, XP SP1 (seldom 98 4.10.2222) Received: from [173.1.104.101] ([173.1.104.101:64534] helo=rproxy2-b-iv.figureone.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 16/EE-32733-C4903A15 for ; Mon, 27 May 2013 03:20:45 -0400 Received: from localhost ([216.220.114.66]) by rproxy2-b-iv.figureone.com (Brand New Heavy v1.0) with ASMTP id MMV16541 for ; Mon, 27 May 2013 00:20:41 -0700 Date: Mon, 27 May 2013 03:20:01 -0400 Reply-To: Sanford Whiteman X-Priority: 3 (Normal) Message-ID: <293168642.20130527032001@cypressintegrated.com> To: =?utf-8?Q?Leszek_Krupi=C5=84ski?= In-Reply-To: <51A2FD10.7030906@gmail.com> References: <51A092FC.4010700@wikimedia.org> <51A1AF3E.5000704@sugarcrm.com> <51A2D395.5030302@sugarcrm.com> <1022965181.20130527011024@cypressintegrated.com> <51A2FD10.7030906@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] date.timezone E_WARNING -- Really necessary? What's the rationale? From: swhitemanlistens-software@cypressintegrated.com (Sanford Whiteman) > In my opinion UTC is a good compromise. I agree that _in the absence of any other setting_ there's nothing wrong with using UTC! Let be clear: UTC is a perfectly fine hands-off default rather than issuing a warning. Non-technical end users will guess you're on London time but whatever. I am simply making the point that UTC is not the "default default" even when sysops or devs put their hands in. The choice isn't just UTC or what the end user personally sets. Domain time exists, no matter if Pierre has experienced it or not. -- S.