Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:56961 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 20030 invoked from network); 20 Dec 2011 11:28:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 20 Dec 2011 11:28:29 -0000 Authentication-Results: pb1.pair.com smtp.mail=derick@php.net; spf=unknown; sender-id=unknown Authentication-Results: pb1.pair.com header.from=derick@php.net; sender-id=unknown Received-SPF: unknown (pb1.pair.com: domain php.net does not designate 82.113.146.227 as permitted sender) X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.113.146.227 xdebug.org Linux 2.6 Received: from [82.113.146.227] ([82.113.146.227:50145] helo=xdebug.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 51/65-16374-C5170FE4 for ; Tue, 20 Dec 2011 06:28:29 -0500 Received: from localhost (xdebug.org [127.0.0.1]) by xdebug.org (Postfix) with ESMTPS id C4DB0DE13E; Tue, 20 Dec 2011 11:28:25 +0000 (GMT) Date: Tue, 20 Dec 2011 11:28:25 +0000 (GMT) X-X-Sender: derick@whisky.home.derickrethans.nl To: Stas Malyshev cc: Will Fitch , Oleg Oshmyan , PHP Developers Mailing List In-Reply-To: <4EE91FDE.1060005@sugarcrm.com> Message-ID: References: <8D58A664-7250-4FEE-9424-2D2DEFC69308@inbox.lv> <1C397FE3-76E2-473B-B47F-194DAF3ACB39@inbox.lv> <4EE91556.3040909@sugarcrm.com> <4EE91FDE.1060005@sugarcrm.com> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] Local time zone From: derick@php.net (Derick Rethans) On Wed, 14 Dec 2011, Stas Malyshev wrote: > > I believe he's referring to sys/time.h, but this introduces > > portability issues. If it were just unix, that would be one thing. > > But maintaining this and a Windows alternative, and I have no idea > > what that is, is not worth it IMO. > > Yes, portability is questionable. Though if we had a good patch that > allows to do it, I don't think it would be too bad to have it. This can never be portable, because Windows doesn't even bother keeping historical timezone rules. They only have: current normal UTC offset, current DST offset and rules on when there is a transition between. Derick