c9e7326275
M-V-B was allowed to lexically and dynamically bind constants in the bytecode compiler and interpreter: > (multiple-value-bind (pi rem) (truncate pi) pi) 3 CLHS says the behavior is undefined when attempting to bind or assign constant variables (CLHS 3.1.2.1.1.3 and the entry for defconstant). The C-compiler gives errors for these sorts of things, and the bytecode compiler and interpreter gives errors when attempting to bind or assign constant variables in lambda expressions, LET, SETQ and various other binding/assignment forms. So the behavior above in M-V-B is inconsistent with the C-compiler and other parts of the bytecode compiler and interpreter. Now give an error when attempting to bind a constant variable in M-V-B in the bytecode compiler and interpreter. |
||
|---|---|---|
| contrib | ||
| doc | ||
| 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.