1. We don't normalize garbage collected entries. Doing that created a false free bucket, so GETHASH and SETHASH stopped searching for entry too early. Fixes #761. 2. MAPHASH does not map over garbate collected entries. Previously MAPHASH did not call copy_entry, so it was always accessing key/val even if they were recently garbage collected, effectively mapping over NIL in the place of the collected value 3. HASH-TABLE-CONTENT had a similar issue to MAPHASH. 4. REMHASH did fill the hole, but didn't replace the moved entry with a free bucket, moreover we've used the value to comptue the hash when computing the distance function. Moreover we introduce an optimization, where SETHASH first tries to fill a garbage collected entry in the bucket before it tries to extend the table. |
||
|---|---|---|
| contrib | ||
| examples | ||
| msvc | ||
| src | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| appveyor.yml | ||
| CHANGELOG | ||
| configure | ||
| COPYING | ||
| INSTALL | ||
| LICENSE | ||
| Makefile.in | ||
| README.md | ||
ECL stands for Embeddable Common-Lisp. The ECL project aims to produce an implementation of the Common-Lisp language which complies to the ANSI X3J13 definition of the language.
The term embeddable refers to the fact that ECL includes a Lisp to C compiler, which produces libraries (static or dynamic) that can be called from C programs. Furthermore, ECL can produce standalone executables from Lisp code and can itself be linked to your programs as a shared library. It also features an interpreter for situations when a C compiler isn't available.
ECL supports the operating systems Linux, FreeBSD, NetBSD, DragonFly BSD, OpenBSD, Solaris (at least v. 9), Microsoft Windows (MSVC, MinGW and Cygwin) and OSX, running on top of the Intel, Sparc, Alpha, ARM and PowerPC processors. Porting to other architectures should be rather easy.