On 03.07.2012, at 18:16, glenpaling wrote:
It's just a bad reference to *self localOffset* rather than the specified offset in todayAtNanoSeconds:offset: (see below). Changing the reference to *aDuration* fixes the problem. Usually todayAtMilliseconds:offset: is used. todayAtNanoSeconds:offset is only used when a call to nowWithOffset: results in the same tick value as the previous call.
todayAtNanoSeconds: nanoSecondsSinceMidnight offset: aDuration
"This is usually only during system startup..." self waitForOffsets. ^ self basicNew setJdn: DaysSinceEpoch seconds: (nanoSecondsSinceMidnight // 1000000000) nano: (nanoSecondsSinceMidnight \\ 1000000000 ) offset: *self localOffset*
Great! Committed to trunk.
This doesn't help with the Chronology test failures. I'll have a look at them.
Glen Paling
Thanks!
- Bert -