The Trunk: Chronology-Core-eem.61.mcz

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

The Trunk: Chronology-Core-eem.61.mcz

commits-2
Eliot Miranda uploaded a new version of Chronology-Core to project The Trunk:
http://source.squeak.org/trunk/Chronology-Core-eem.61.mcz

==================== Summary ====================

Name: Chronology-Core-eem.61
Author: eem
Time: 5 October 2020, 10:19:35.996376 pm
UUID: 13de44be-afb9-4f0f-81b1-5f3f8fa821db
Ancestors: Chronology-Core-dtl.60

Provide Time class>>millisecondClock and DateAndTime class>>millisecondClock to indicate that this is now a proiper clock.  It will not roll-over after 45 days like the old 30 bit millisecond clock.

Nw code should use millisecondClock, not millisecondClockValue, and old code (senders of millisecondClockValue) should be migrated whenever convenient.

=============== Diff against Chronology-Core-dtl.60 ===============

Item was added:
+ ----- Method: DateAndTime class>>millisecondClock (in category 'smalltalk-80') -----
+ millisecondClock
+
+ ^self clock millisecondClock!

Item was added:
+ ----- Method: Time class>>millisecondClock (in category 'general inquiries') -----
+ millisecondClock
+ "Answer the value of the millisecond clock. Unlike older implementatins, this is a clock; it will never roll-over."
+
+ ^self utcMicrosecondClock // 1000!


Reply | Threaded
Open this post in threaded view
|

Re: The Trunk: Chronology-Core-eem.61.mcz

Nicolas Cellier


Le mar. 6 oct. 2020 à 07:19, <[hidden email]> a écrit :
Eliot Miranda uploaded a new version of Chronology-Core to project The Trunk:
http://source.squeak.org/trunk/Chronology-Core-eem.61.mcz

==================== Summary ====================

Name: Chronology-Core-eem.61
Author: eem
Time: 5 October 2020, 10:19:35.996376 pm
UUID: 13de44be-afb9-4f0f-81b1-5f3f8fa821db
Ancestors: Chronology-Core-dtl.60

Provide Time class>>millisecondClock and DateAndTime class>>millisecondClock to indicate that this is now a proiper clock.  It will not roll-over after 45 days like the old 30 bit millisecond clock.

Nw code should use millisecondClock, not millisecondClockValue, and old code (senders of millisecondClockValue) should be migrated whenever convenient.

=============== Diff against Chronology-Core-dtl.60 ===============

Item was added:
+ ----- Method: DateAndTime class>>millisecondClock (in category 'smalltalk-80') -----
+ millisecondClock
+
+       ^self clock millisecondClock!

Item was added:
+ ----- Method: Time class>>millisecondClock (in category 'general inquiries') -----
+ millisecondClock
+       "Answer the value of the millisecond clock. Unlike older implementatins, this is a clock; it will never roll-over."
+1

Oh, but didn't traditional clock use to rollover every 12 hours or so ? ;)

+
+       ^self utcMicrosecondClock // 1000!