objc: Objective-C to Lisp Binding with Transparent Layer
https://github.com/apr3vau/objc
Discussions: https://discu.eu/q/https://github.com/apr3vau/objc
Sorta started .. but man, ansi-test is kinda annoying in how it loads things. LOAD for the win or something, no DEFSYSTEM or anything .. sighs. #Lisp #CommonLisp #LispM #LispMachine
Read CSV files in Common Lisp (cl-csv, data-table)
https://dev.to/vindarel/read-csv-files-in-common-lisp-cl-csv-data-table-3c9n
Discussions: https://discu.eu/q/https://dev.to/vindarel/read-csv-files-in-common-lisp-cl-csv-data-table-3c9n
More complete benchmark after fixing some issues.
Blue -- current develop branch
Orange -- after moving locals to stack
The plot is made with polyclot, results are normalized and faceted (wrap, 11 tests per panel).
LucidPlan proudly announces version v0.3.8 of the project:
https://codeberg.org/jjba23/lucidplan
#foss #project #management for everyone ( #selfhosting )
work more #agile in your team thanks to a fast-paced no-nonsense-workflow and customizability, also thanks to being written in #lisp ( #guile #scheme ) and using #guix
This tool results of years of experience using proprietary systems like Jira/Trello, and experiencing the frustrations they bring.
find my live instance here:
I almost done with the first viable version of our new testing library, so you'll be able to sleep in peace soon.
https://git.sr.ht/~abcdw/guile-ares-rs/tree/master/item/test/guile/ares/suitbl-test.scm#L253
I beg you not to use it (yet), I break API daily or at least I try to do so.
Reification of continuations lets you do some neat things.
This took me three months (a month longer than I had hoped), but I finally have merged it into the main branch!
This patch rewrites the Emacs Lisp lexer and parser in Scheme using Scheme code that is 100% compliant with the #R7RS standard, so it should now work across all compliant Scheme implementations. Previously the old parser relied on #Guile -specific regular expressions.
This patch also implements a new feature where a stack trace is printed when an error occurs. This of course makes debugging much, much easier. Previously the old parser did not keep track of where code evaluation was happening, it simply produced lists without source location information. The new parser constructs an abstract syntax tree (AST) and source locations are attached to the branches of the tree which can be used in error reporting and stack traces.
Next I will make whatever minor tweaks might be necessary to get my Emacs Lisp interpreter run on other Scheme implementations, in particular MIT Scheme, Gambit, Stklos, and Gauche. I would also like to try to get it running on Chicken and Chez, although these are going to be a bit more tricky.
Then I will continue with the task of implementing a new declarative GUI library.
Did you know Racket runs on the Raspberry Pi?
IDE, compiler, libraries and documentation included for stand alone use.
32-bit ARMv6 VFP (built on Raspbian) at https://users.cs.utah.edu/plt/snapshots/current/installers/racket-8.17.0.2-arm-linux-cs.sh via https://snapshot.racket-lang.org
@raspberrypi.com @Raspberry_Pi #raspberrypi #racketlisp #lisp #drracket
Transparent UIs (Lisps, REPLs, and Emacs mentioned)
https://aartaka.me/transparent-ui.html
Discussions: https://discu.eu/q/https://aartaka.me/transparent-ui.html
At some point within the last year I've realized that one can learn #languages for fun and I have to admit that learning another programming language is not that interesting anymore. I still like #lisp, because it is so comfortable to write for small utils, but otherwise I would just set on something like #golang for personal stuff and not care anymore. It is good enough of a tool. Or whatever language is required.
There's more to avoiding calling Lisp homoiconic because it's an inaccurate or incomplete characterization. As Shriram Krishnamurthi @shriramk points out, this misses the point of why Lisp languages are different. To capture this he introduces the concept of "bicamerality".
https://parentheticallyspeaking.org/articles/bicameral-not-homoiconic
LispUsers is a collection of user contributed software that has been shipping with Interlisp and later Medley since the 1970s. To load a LispUsers program evaluate (IL:FILESLOAD file) where `file` is the program name without extension. Most come with .pdf or .TEDIT documentation that explains how to run the program.
Bootstrapping Lisp in a Boot Sector
https://github.com/jart/sectorlisp
Discussions: https://discu.eu/q/https://github.com/jart/sectorlisp
Bootstrapping Lisp in a Boot Sector
Link: https://github.com/jart/sectorlisp
Discussion: https://news.ycombinator.com/item?id=43892773