sbcl
cl-ppcre
Our great sponsors
sbcl | cl-ppcre | |
---|---|---|
59 | 13 | |
1,764 | 291 | |
1.2% | 2.1% | |
9.9 | 0.0 | |
6 days ago | 10 months ago | |
Common Lisp | Common Lisp | |
GNU General Public License v3.0 or later | 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.
sbcl
-
Arena Allocation in SBCL
Based on the commit message [0], and the references to "user code" in this document, my guess is that user programs have or will have access, but it's not finalized enough to be documented.
That being said, I suppose if you're developing an internal API for a compiler/interpreter, your "users" could be other parts of the project rather than language users.
https://github.com/sbcl/sbcl/commit/7f65522a16d857e41aa61cd0...
- Implementing Interactive Languages
-
Garbage Collection in a Large Lisp System (1984) [pdf]
related: the Immix inspired parallel-mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently into SBCL.
https://github.com/sbcl/sbcl/blob/master/doc/internals-notes...
https://applied-langua.ge/~hayley/swcl-gc.pdf
build with
./make.sh --without-gencgc --with-mark-region-gc (on x86-64/Linux and x86-64/macOS only at the moment).
-
SBCL: merge of mark-region GC
The Immix inspired mark-region GC developed by Hayley Patton (https://github.com/no-defun-allowed/swcl) got merged recently, which is pretty cool news for SBCL users.
- Owner of Symbolics Lisp machines IP is interested in a non-commercial release
- Steel Bank Common Lisp
-
Wasix, the Superset of WASI Supporting Threads, Processes and Sockets
>Just like your usual hardware CPU cannot run Common Lisp directly, neither can WASM.
My usual hardware CPU runs Common Lisp code beautifully, thanks to this native x86-64 compiler: https://www.sbcl.org/
-
Common Lisp – Myths and Legends
You can get SBCL for free which actually beats Lispworks on performance AFAIK: https://www.sbcl.org/
-
Turning Linux Into a Usable Lispy Machine?
sbcl w/ linedit for repl/shell
cl-ppcre
-
Compile time regular expression in C++
I've never used cl-ppcre myself, but its docs[1] claim that it provides compile-time regexes:
> CL-PPCRE uses compiler macros to pre-compile scanners at load time if possible. This happens if the compiler can determine that the regular expression (no matter if it's a string or an S-expression) is constant at compile time and is intended to save the time for creating scanners at execution time (probably creating the same scanner over and over in a loop).
This has been available in Lisp since at least 2004.
- Ask HN: What are some of the most elegant codebases in your favorite language?
-
sbcl and Let Over Lambda
A few weeks back Xach recommended cl-ppcre which i found educational.
-
-🎄- 2022 Day 1 Solutions -🎄-
For simple string processing, there are some functions in the language, that you can find listed here (for string-specific functions) and here (for more generic sequence-handling functions). For anything involving regular expressions, cl-ppcre is the way, in particular the split and register-groups-bind functions.
-
The unreasonable effectiveness of f-strings and re.VERBOSE
If the regular expression engine accepted tree structures instead of just strings, you could have first class definitions of fragments of regular expressions. Even better, you could define them as functions, so you could have parameterized fragments. So then you could just do something like http://edicl.github.io/cl-ppcre/#create-scanner2 without the bizarre definition syntax above.
I must have a serious bug in my writing about this, because this was never about regex engines -- it's about literals and domain-specific sublanguages in general. Composing DSL programs by string concatenation is such a famous source of security bugs you see it in top-10 lists. I linked to the very similar example of a PEG parsing DSL.
But any regex engine that can work with a parse tree shows the same principle, e.g. https://edicl.github.io/cl-ppcre/#create-scanner2
-
Stas has alienated long-time ASDF maintainer Robert Goldman
Could you just direct me to some existing discussions, in order to save time? I already read this one.
That thread is not complete context; see also e.g. https://github.com/edicl/cl-ppcre/pull/30 and https://github.com/edicl/cl-fad/pull/24.
-
#"<your literal interpretation here>" (regular expression literals)
I plan to use the regular expressions with a cl-ppcre wrapper, also emulating various clojure regular expression operations. Similar to re21, which doesn't quite support the operations in the way I'd like (or match the clojure operations), and whose regular expression literal syntax is "#//".
What are some alternatives?
ccl - Clozure Common Lisp
abcl - Armed Bear Common Lisp <git+https://github.com/armedbear/abcl/> <--> <svn+https://abcl.org/svn> Bridge
sb-simd - A convenient SIMD interface for SBCL.
BQN - An APL-like programming language. Self-hosted!
maiko - Medley Interlisp virtual machine
seed7 - Source code of Seed7
common-lisp-jupyter - A Common Lisp kernel for Jupyter along with a library for building Jupyter kernels.
lisp-xl - Common Lisp Microsoft XLSX (Microsoft Excel) loader for arbitrarily-sized / big-size files
cloc - cloc counts blank lines, comment lines, and physical lines of source code in many programming languages.
portacle - A portable common lisp development environment
sbcl-problem-on-AppleM1 - Problem on SBCL/M1 Mac
qlot - A project-local library installer for Common Lisp