On 12-01-2013, at 6:39 AM, "David T. Lewis" <lewis at mail.msen.com> wrote:

> Um ... I'm a little confused myself at this point, I'm not sure what
> has changed here. But I'm quite confident that in practice ioSeconds()
> has been answering seconds from the "Smalltalk epoch" relative to local
> time zone for a many years (probably since the first Squeak VMs). 


Me too. I see the ioSeconds() code in the other platforms, I have the history of my code, I have memories of never noticing the time being wrong and I just can't make sense of it…

Anyway, I've changed my code, it reports a good time on my Pi, in a 4.0 image, so I'm content for now. Some puzzles simply aren't worth the effort of finding a complete solution-set.

I see there are some other problems with time coming up for discussion but I think I'll worry about that later when I get the next set of VM stuff working.

tim
--
tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
"Virtual Memory" means never knowing where your next byte is coming from.