Good catch, thank you. The only remaining use of DateAndTime>>ticks is in
storeDataOn: for serializing instances in the known earlier format. That
is a good standard to use for compatibility, and works well as an external
storage format anyway.
Dave
On Sun, Sep 06, 2020 at 12:29:23PM +0000,
[hidden email] wrote:
> Levente Uzonyi uploaded a new version of Chronology-Core to project The Trunk:
>
http://source.squeak.org/trunk/Chronology-Core-ul.58.mcz>
> ==================== Summary ====================
>
> Name: Chronology-Core-ul.58
> Author: ul
> Time: 6 September 2020, 2:28:59.102076 pm
> UUID: 67bb8acc-c81b-4e0c-a6f2-e9603c284236
> Ancestors: Chronology-Core-dtl.57
>
> Simplify DateAndTime class>>unixEpoch
>
> =============== Diff against Chronology-Core-dtl.57 ===============
>
> Item was changed:
> ----- Method: DateAndTime class>>unixEpoch (in category 'squeak protocol') -----
> unixEpoch
> "Answer a DateAndTime representing the Unix epoch (1 January 1970, midnight UTC)"
>
> + ^self utcMicroseconds: 0 offset: 0!
> - ^ self basicNew
> - ticks: #(2440588 0 0) offset: Duration zero;
> - yourself.
> - !
>
>
Locked
