Hello everyone, We are happy to announce the first release candidate of the upcoming CHICKEN 5.2.0.
CHICKEN 5.2.0rc1 is now available at this location: https://code.call-cc.org/dev-snapshots/2020/01/12/chicken-5.2.0rc1.tar.gz The SHA256 sum of that tarball is bf651739d7b1588b9f8b860975171987cb81566627f6fbcdf956637d35089bdc This is mostly a maintenance and bugfix release. One important change might cause breakage of existing code: CHICKEN will now error out when you use -c with multiple files (see #1655) for more info. Another change that might expose bugs in existing code, thereby possibly breaking it is that modules won't pollute the global namespace anymore when imported. This may expose missing imports in macro code, because an import won't make the imports available for compile-time code. See #1548 for more info. The complete list of changes since version 5.1.0 is available here: https://code.call-cc.org/dev-snapshots/2020/01/12/NEWS Please give it a test and report your findings to the mailing list. Here's a suggested test procedure: $ make PLATFORM=<platform> PREFIX=<some dir> install check $ <some dir>/bin/chicken-install pastiche If you want to build CHICKEN with a compiler other than the default one, just use C_COMPILER=<the compiler> (e.g., C_COMPILER=clang) on the make invocation. Of course, feel free to explore other supported build options (see the README file for more information) and actually use CHICKEN 5.2.0rc1 for your software. If you can, please let us know the following information about the environment you tested the RC tarball on: Operating system: (e.g., FreeBSD 12.0, Debian 9, Windows 10 mingw-msys under mingw32) Hardware platform: (e.g., x86, x86-64, PPC) C Compiler: (e.g., GCC 6.4.0, clang 5.0.0) Installation works?: yes or no Tests work?: yes or no Installation of eggs works?: yes or no Thanks in advance! The CHICKEN Team
signature.asc
Description: PGP signature