We should go through the system and look at what we have, then make logical names. Right now the modules supplied by core are somewhat arbitrarily named, and too many unrelated things are grouped together. Of course, if you want to tackle one of these before, feel free to submit a patch. These should be considered after CHICKEN 5 is released.
Basically everything that's currently being done through ugly #compiler# hacks should have a supported, documented way to do it. Define an "official API" for users of the compiler.This work has been completed: the compiler now is composed of modules in the chicken-5 branch (prefixed with piler), but the following "nice to haves" are not yet implemented: Please, no editing flamewars here! Modularising the compiler
Are code chicken lib and code chicken core the same how to#
Feel free to add more details if you know of a way to implement something or have an idea how to improve some part. Here's a proposed list of things we would like to see in CHICKEN 5. Check if it is possible to have both CHICKEN 4 and CHICKEN 5 installed system-wide.Determine how to make CHICKEN 4 eggs live alongside CHICKEN 5 eggs.Make set!-ing of module-defined identifiers an error.Make set!'ing of unbound variables an error.Make the library load path a search path.Reworking the way libraries are loaded.queue datatype (data-structures), binary-search (data-structures), mmapped files (posix), object-evict (lolevel).Refactoring the CHICKEN test suite to use a core library?.Replacing SRFI-14 with cset implementation from irregex?.
0 kommentar(er)
