ctype
Eclector
Our great sponsors
| ctype | Eclector | |
|---|---|---|
| 2 | 4 | |
| 25 | 104 | |
| - | 0.0% | |
| 6.2 | 7.8 | |
| 22 days ago | about 2 months ago | |
| Common Lisp | Common Lisp | |
| BSD 2-clause "Simplified" License | BSD 2-clause "Simplified" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ctype
-
Re-targeting (Lisp) compilers
There is significant overlap with SICL and its associated pieces which supply many of the other parts needed to make a Common Lisp. Some of these are Cluster which provides a portable and extensible assembler, Eclector which supplies a portable and extensible reader, Concrete-Syntax-Tree that supports source code tracking during compilation, ctype that implements the Common Lisp type system, and Clostrum that provides first-class environments for e.g. run-time, evaluation, and compilation. The SICL project has as one of its goals the creation of portable infrastructure for implementing Common Lisp, and these pieces are novel building blocks that were created as part of the project.
-
Common Lisp polymorphic stories.
Other times, the support is limited by the implementations supported by ctype and cl-form-types (and cl-environments). Although, if there is any good request, I could work on making a dynamic-only ANSI-CL compliant sub-system of PF.
Eclector
-
Csexp: S-Expressions over the Network
I think this should be safe: https://github.com/phoe/safe-read
This doesn’t provide such functionality out of the box, but it makes it pretty trivial to produce a custom READ that only has the features you want: https://github.com/s-expressionists/Eclector
-
Re-targeting (Lisp) compilers
There is significant overlap with SICL and its associated pieces which supply many of the other parts needed to make a Common Lisp. Some of these are Cluster which provides a portable and extensible assembler, Eclector which supplies a portable and extensible reader, Concrete-Syntax-Tree that supports source code tracking during compilation, ctype that implements the Common Lisp type system, and Clostrum that provides first-class environments for e.g. run-time, evaluation, and compilation. The SICL project has as one of its goals the creation of portable infrastructure for implementing Common Lisp, and these pieces are novel building blocks that were created as part of the project.
-
Are there public experiments with parallel and concurrent lisp 'engines'?
You mean the parts of the reader that is capable of reading from a stream object and returns strings, booleans, numbers? These are just functions that accept a stream and they return Lisp objects. See e.g. Eclector for an implementation of a Lisp reader as an external library.
-
Lowercased version of Common Lisp with case preserving readtable (:PRESERVE)
I'm aware of eclector; hoping to take a look some day.
What are some alternatives?
fast-generic-functions - Seal your generic functions for an extra boost in performance.
SICL - A fresh implementation of Common Lisp
lisp-interface-library - LIL: abstract interfaces and supporting concrete data-structures in Common Lisp
lparallel - Parallelism for Common Lisp
sealable-metaobjects - A CLOSsy way to trade genericity for performance.
nyxt - Nyxt - the hacker's browser.
polymorphic-functions - A function type to dispatch on types instead of classes with partial support for dispatching on optional and keyword argument types.
luckless - Lockless data structures for Common Lisp
Concrete-Syntax-Tree - Concrete Syntax Trees represent s-expressions with source information
wat-js - Concurrency and Metaprogramming for JS
generic-cl - Generic function interface to standard Common Lisp functions
cl-secure-read - Securing a reader in spirit of Let Over Lambda