fdf7c77909
OP_FLET previously had to first create functions referencing the env "before" and then add these functions to the env "after". This is because we were addressing from the stack top: env: bottom[0:var]top fn1: ref(top-1) fn2: ref(top-1) env: bottom[0:var, 1:fn1, 2:f2n]top Otherwise fn2 referencing top-1 would point to fn1 instead of var. Now that locals are addressed from the stack bottom we can add functions eagerly to locals without consing intermediate sequence of functions: env: bottom[0:var]top fn1: ref(bottom+0) env: bottom[0:var, 1:fn1]top fn2: ref(bottom+0) env: bottom[0:var, 1:fn1, 2:f2n]top That saves us one loop (nfun iterations). A similar observation applies to LABELS, although we still need the closure fixup because earlier function may reference a function defined later, so we still need a second loop. That said we don't have to cons a separate sequence of functions, because we may iterate over locals vector instead. Both changes save us from an operator that adds a collection to the lcl_env, so we remove tack_lcl macro and its expansion function foot_lcl. |
||
|---|---|---|
| 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.