From: | Peter Bex |
Subject: | [Chicken-users] [ANN] CHICKEN 5.0.0 has been released |
Date: | Wed, 7 Nov 2018 19:53:30 +0100 |
User-agent: | NeoMutt/20170113 (1.7.2) |
Dear CHICKEN users, We are proud to announce the immediate availability of CHICKEN 5.0.0 at the following URL: https://code.call-cc.org/releases/5.0.0/chicken-5.0.0.tar.gz This tarball has the following SHA256 checksum: a8b94bb94c5d6a4348cedd75dc334ac80924bcd9a7a7a3d6af5121e57ef66595 It has been a long stretch, but we finally made it! This release contains the largest number of big-impact changes we've made since the CHICKEN 4.0.0 release. Most importantly, we have completely overhauled the module layout so that it should make more sense where each identifier is located. For a quick overview of where things are, see the page we used for discussion of these changes: https://wiki.call-cc.org/core-libraries-reorganization The manual has of course also been updated to reflect these new modules: https://wiki.call-cc.org/man/5/Included%20modules Other notable features are: - Full numeric tower - A new declarative egg description format for chicken-install - Improved support for static linking (eggs are now also compiled statically) - "Deployment" mode has been dropped as it was less portable and reliable than static linking. - Builds are fully bit-for-bit reproducible (for core, but user code too) - Random numbers now use a better PRNG than libc rand() (namely, WELL512) - Core has gone on a diet: several libraries have been moved to eggs, like srfi-1, srfi-13, srfi-14, srfi-18, srfi-69, and several other things. The (very long!) complete list of changes since version 4.13.0 is available here: https://code.call-cc.org/dev-snapshots/2018/08/11/NEWS Because the testing period has been quite long, we've managed to port many of the most important eggs to CHICKEN 5 already. You can view them at the new subdomain, see https://eggs.call-cc.org/5 Of course for the time being, not everyone can immediately switch to CHICKEN 5 for everything, so https://eggs.call-cc.org/4 also works. If you have code you want to port, we've created a porting guide that covers the most important pitfalls: https://wiki.call-cc.org/porting-c4-to-c5 Many thanks to everyone in the community for their enthusiasm, mental support and help with testing all this new code and enthusiastically porting stuff to CHICKEN 5 even back when it was barely ready! Regards, The CHICKEN Team
signature.asc
Description: PGP signature