|5 days ago||12 days 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.
Permissive Licenses are Counterintuitive
3 projects | reddit.com/r/linux | 17 Jun 2022
But sometimes, there are other incompatible licenses, even for open source software. Sometimes, even if you could build a derived work under GPL, nobody wants to maintain that fork when they could keep using a more-permissive one. So, for example, SBCL is under BSD and public domain licenses, so it doesn't link against Readline. Which makes it really unpleasant to use directly -- if you're used to REPLs from things like Ruby or Python, one where you can't even hit left-arrow while editing a line just seems stupid.
What would it take to make this code work? (a question on cross-compilation)
1 project | reddit.com/r/Common_Lisp | 14 Jun 2022
SBCL apparently *does* support cross-compilation of SBCL itself, if this https://github.com/sbcl/sbcl/tree/master/crossbuild-runner is what I think it is. I wonder how much that is used in practice...
New to lisp. Not new to programming.
4 projects | reddit.com/r/lisp | 24 May 2022
Has an obvious answer? See https://github.com/sbcl/sbcl/graphs/contributors
Just found this sub!
1 project | reddit.com/r/emacs | 19 Apr 2022
If you like Lisp languages, Emacs is great, Steel Bank Common Lisp (SBCL) is great, Guile Scheme is great.
The SBCL repository reaches 20,000 commits
1 project | reddit.com/r/Common_Lisp | 19 Feb 2022
Sbcl require asdf failing build
2 projects | reddit.com/r/Common_Lisp | 8 Feb 2022
More information about SBCL is available at .2 projects | reddit.com/r/Common_Lisp | 8 Feb 2022
sbcl --dynamic-space-size 3072 --no-userinit --non-interactive --eval '(load #p"/home/bhaskar/Downloads/asdf-3.3.5/build/asdf.lisp")'/Downloads/asdf-3.3.5/build/asdf.lisp")' This is SBCL 2.1.4, an implementation of ANSI Common Lisp. More information about SBCL is available at http://www.sbcl.org/. SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information.
Common Lisp Windows 10 install
3 projects | reddit.com/r/Common_Lisp | 25 Jan 2022
You can go to https://github.com/sbcl/sbcl -> Actions -> Windows and enter e.g. branch:sbcl-2.2.0 into the "Filter workflow runs" textfield. This will lead you to https://github.com/sbcl/sbcl/actions/runs/1638267807. From there you can download a Windows installer for SBCL 2.2.0.
What are some of the best resources to get started in scheme?
1 project | reddit.com/r/scheme | 19 Jan 2022
Python bytecode explained
4 projects | reddit.com/r/programming | 16 Jan 2022
See e.g. CMUCL and its latter day fork SBCL, type inferencing native lisp compilers (which also had a lot of influence on the direction of various other Lisp and other language compilers).
The unreasonable effectiveness of f-strings and re.VERBOSE
4 projects | news.ycombinator.com | 23 May 2022
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.4 projects | news.ycombinator.com | 23 May 2022
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
Adding Space to subst function
1 project | reddit.com/r/lisp | 12 Apr 2022
Take a look at - https://github.com/edicl/cl-ppcre
Common Lisp ASDF maintainer considers resignation
1 project | reddit.com/r/lisp | 22 Jan 2022
And here's what I believe represents the reality of the situation... Stas was indeed tired of ASDF's changes. Now the nature of what changes to make is a matter of judgement of course, but in this case (I'm thinking of SBCL's bug report request to update ASDF: https://bugs.launchpad.net/sbcl/+bug/1826074), it would be a different matter altogether if the discussion was centered on how best to make the new ASDF work with SBCL, but the thread reads to me like a man who had to put up with too much breakage for the upteenth time. Now, if (for the sake of argument :D) the change was of the necessary kind -- think hardware changes or security issues -- I can still see myself feeling wronged, it's human to do so. Because I don't trust ASDF anymore or I feel as if they (or other people at each step of the process) have not shared enough of the burden. But from the discussions I have read (https://github.com/edicl/cl-ppcre/pull/30) what the ASDF maintainers want to change does not seem unreasonable and they are willing to share the burden. But let us say it's truly a 50/50 deadlock. Well then Linus is right, show us the code, who dares wins. And Stas certainly has enough on his plate. But that's why we must cooperate. You don't have to be a diplomat to know the difference when two people want to work together and when one party wants out. And this setting makes more sense when you read (https://bugs.launchpad.net/sbcl/+bug/1823442) where Stas honestly states he wants nothing more to do with ASDF. I don't think it's unreasonable to surmise there's a bit more going on here than plainly technical issues.
Stas has alienated long-time ASDF maintainer Robert Goldman
6 projects | reddit.com/r/Common_Lisp | 9 Jan 2022
Could you just direct me to some existing discussions, in order to save time? I already read this one.6 projects | reddit.com/r/Common_Lisp | 9 Jan 2022
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)
2 projects | reddit.com/r/lisp | 4 Jul 2021
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.
common-lisp-jupyter - A Common Lisp kernel for Jupyter along with a library for building Jupyter kernels.
BQN - An APL-like programming language. Self-hosted!
maiko - Medley Interlisp virtual machine
lisp-xl - Common Lisp Microsoft XLSX (Microsoft Excel) loader for arbitrarily-sized / big-size files
seed7 - Source code of Seed7
portacle - A portable common lisp development environment
qlot - A project-local library installer for Common Lisp
Co-dfns - High-performance, Reliable, and Parallel APL
cloc - cloc counts blank lines, comment lines, and physical lines of source code in many programming languages.