Chronos is one of the many Smalltalk-related blogs syndicated on Planet Smalltalk

Discussion of the Essence# programming language, and related issues and technologies.

Blog Timezone: America/Los_Angeles [Winter: -0800 hhmm | Summer: -0700 hhmm] 
Your local time:  


Version B1.188 of the Chronos Date/Time Library Published

Chronos Version B1.188 has been publised ("Beta Release 1--build 188".) Chronos B1.188 is available for VisualWorks, Squeak and Dolphin. The Chronos Seed Archive for B1.188 is also available (the "Chronos Seed" is the platform-independent Chronos codebase, used for porting Chronos from VisualWorks to other Smalltalk pltatforms.)

Chronos Version B1.188 can be obtained from the Chronos Web Site. The VisualWorks version can also be obtained from the Cincom Public StORE Repository, and the Squeak version can also be obtained from SqueakMap (as a .sar archive.)

NOTE: The SqueakMapPackageLoader tool does not work with the Chronos.sar archive, although Chronos.sar can be dowloaded to your local machine over HTTP and then installed using the Squeak FileList. (This problem has been reported, and a fix has been identified. See: [SM][BUG] Error: can't find EOCD position.)

You may also use the direct download link for VisualWorks, the direct download link for Squeak or the direct download link for Dolphin.

The Chronos Time Zone Repository is included in the download archive. Be sure to follow the Chronos Installation Instructions--especially if you have not already done so for a previous version of Chronos.

If you are reinstalling Chronos into an image in which an earlier version is already resident, and do not install the new version from the Cincom Public StORE Repository using StORE, it is necessary to first remove the earlier version. StORE has been able to correctly install the new version on top of every earlier version I have tried--but I haven't tried them all.

About Chronos Version B1.188

Chronos Version B1.188 makes Chronos Timeperiods (general-purpose time intervals) fully conform to the semantics and API of CalendricalCoordinates (instances of YearMonthDay and Timepoint.)

Timeperiod is now subclassed under CalendricalCoordinate, instead of under TemporalInterval. Significant method refactoring was done. The result is that instances of Timeperiod, YearMonthDay and Timepoint are now essentially completely type compatible as far as the public API is concerned.

I will soon be posting a blog entry that will discuss time intervals in Chronos in greater depth. This will be the third article in the "Chronos 101" series that was started a week ago.

Also, the ChronosParser was enhanced to more intelligently reduce the generality of parsed date/time values. For example, when asked to parse a full DateAndTime value, ChronosParser will now answer a YearMonthDay instead, in cases where no time-of-day values or time zone are specified in the source text.

During unit testing of the above, a few pre-existing bugs were found and fixed.

Finally, note that the Executable Examples have been updated.

No comments: