b7eaf35502
The .byte_stack is used only by files to: a) unread a single octet when we use fallback LISTEN implementation b) unread bytes that make a character when UNREAD-CHAR is used The latter is important to transcode characters from one external format to another (i.e see the test external-format.0003-transcode-read-char). This commit improves the function unread-byte to do the same brinding bivalent streams almost to parity with regard to that implementation (see next commit). That makes the implementation of eformat cleaner, .byte_stack more self-contained, and saves us consing new byte stack for sequence streams (where it was simply ignored, not to mention not entirely correct - because we've used a .byte_stack length to decrement the pointer position while the byte could have more bits than one octet). Other optimizations that could be done here: - make the byte stack an adjustable vector to avoid consing on each unread |
||
|---|---|---|
| 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.