Time primitives

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
21 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Time primitives

Bert Freudenberg

> On 10.04.2015, at 02:39, David T. Lewis <[hidden email]> wrote:
>
> On Thu, Apr 09, 2015 at 12:04:53PM +0200, Bert Freudenberg wrote:
>>> On 08.04.2015, at 14:06, David T. Lewis <[hidden email]> wrote:
>>> On Wed, Apr 08, 2015 at 10:56:13AM +0200, Bert Freudenberg wrote:
>>>>
>>>> In Trunk, #useLocale is disabled (enabled in Etoys). Are we seriously all
>>>> using +01:00 times, and still expecting users to set the right time zone manually?!
>>>
>>> That's a problem for sure, we should fix it in the upcoming release
>>
>> So you're in a far away time zone, right?
>
> Why no, not at all. My time zone is right here in Michigan. It's all
> the rest of you that are far away ;-)
Midwestern-centric earth model ... why not ;-)

>> And yours still gets reported as +01:00?
>>
>
> Yes, that's right. With a SqueakTrunk image, I get this:
>
>  DateAndTime now ==> 2015-04-09T19:52:01.01+01:00
>
> But it should be this:
>
>  DateAndTime now ==> 2015-04-09T19:52:01.01-04:00
>
> If I enable the useLocale preference, I get the correct time zone offset:
>
>  DateAndTime now ==> 2015-04-09T19:58:05.576-04:00
Well, if nothing else breaks, then maybe enabling useLocale is the simplest fix right now?

It will not deal with time zone changes while the image is running, since it's only used on startup.

- Bert -






smime.p7s (5K) Download Attachment
12