Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62744
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.20.127 cause and error)
Message-ID: <5044BFA7.8070908@lsces.co.uk>
Date: Mon, 03 Sep 2012 15:33:11 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120604 Firefox/13.0 SeaMonkey/2.10
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <CAArmra3oN6NMn-CPn95piNQeKN1LJ7nq3baj1B0z6pCCPZX0VQ@mail.gmail.com> <CAEPJdunLROfKuGNu3AjCjLY3KmQ4DyHJi04WkENyVg6zapVrAg@mail.gmail.com> <50436412.7010802@ajf.me> <alpine.DEB.2.02.1209021814580.25835@whisky.home.derickrethans.nl> <5043C3E9.2010105@ajf.me> <alpine.DEB.2.02.1209022145220.25835@whisky.home.derickrethans.nl> <5043C5AF.3060701@ajf.me> <alpine.DEB.2.02.1209022149540.25835@whisky.home.derickrethans.nl> <5043C74C.8020400@ajf.me> <alpine.DEB.2.02.1209022213180.25835@whisky.home.derickrethans.nl> <CAPg3Xx+YDJQ2buTJN9OBJ6fos+mDdxD9wdWueOZ9+d_qyuP3iA@mail.gmail.com> <5043D8C0.3020802@lsces.co.uk> <CAArmra3Oj7LfMKOf9mZpYnd6xzdhUvUPOOJLS69EbMwcc7EkNA@mail.gmail.com> <alpine.DEB.2.02.1209030912170.25835@whisky.home.derickrethans.nl> <CAArmra12C2Y7SCJD9xoCBqveLsAQLyvQWaF4hpYYu7+hu8w9uA@mail.gmail.com> <alpine.DEB.2.02.1209031251110.25835@whisky.home.derickrethans.nl> <5044A261.10901@lsces.co.uk> <CAArmra2L5uHUdqksMM2572iAMQAvFW3zogSeKT=cYxnihRYfdA@mail.gmail.co
 m>
In-Reply-To: <CAArmra2L5uHUdqksMM2572iAMQAvFW3zogSeKT=cYxnihRYfdA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RFC for Adding __toString to DateTime
From: lester@lsces.co.uk (Lester Caine)

Will Fitch wrote:
>
> Hi, Lester - I'll update the patch and RFC to include this format.  This is the
> format I'll use unless others have a better approach:
>
> 2012-09-01T00:00:00-0500 (America/Chicago)

Either offset OR timezone ... not both ... BUT as Derick has pointed out ... 
without the offset, we don't know it is offset from UTC so you end up needing 
both. This is where there is still a lot of disagreement on short codes for 
normal and DST settings and a lot of clashes. NORM/DST is more help than the 
offset ... ( And seconds for Lars )

However the other thing to bear in mind here is that if you don't set a timezone 
for the datetime object then you just get a simply local time and do not want to 
display a timezone at all. I think it more likely that people will be doing that 
as much as are actually displaying a timezone? I would probably expect as many 
people don't want TZ as do? Derick will probably say you should not use it like 
that ;) but I only setTimezone on the display side when I need to convert from 
UTC. Simple single time zone setups don't need to worry about daylight saving so 
just working with a simple 'clock' is practical.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk