I wanted to try #clisp instead of #sbcl yesterday. Turns out it's compiled without POSIX threads support in #debian, so no Bordeaux-threads and I'm too #lazy to recompile it...

#commonlisp #lisp

64 core monster, half a TB of RAM, NVME disks…. And #sbcl takes 20 minutes to compile (#GNU #clisp — I like you but you’re slow!)

CL packages are the wrong way to implement packages in Lisp. As I explained in a discussion two years ago, packages implemented using obarrays (or equivalent) don’t work reliably.

We have a much better basis for Lisp packages in the shorthands mechanism. It only needs to be completed.

Richard Stallman on CL packages landed
#clisp #emacs
https://andreyor.st/posts/2022-11-01-emacs-lisp-shorthands-as-namespacing-system/

> The reason namespaces systems do not fit well into #Lisp is that they have to operate in ‘read’, in the choice of which symbol object you get.

Richard Stallman on Emacs Lisp's future

@lxsameer that's cool! I *recently* started using #emacs because I found file navigation annoying in other IDEs. I know how to touch type, so now I literally just have to type in what I want (with all the autocompletion benefits just like a shell). Still learning the basics but finding even that awesome!

By the way, I've been programming a bit of #Clojure too, although right now I prefer the #clisp vibes :clojure: :lisp:

clisp -modern -E UTF-8

#clisp #commonLisp #lisp #localisation #youCouldHaveHadMyZorkmids

Bloody well written ..

https://nyxt.atlas.engineer/article/elisp-vs-common-lisp.org

#nyxt #browser #elisp #clisp #opensource

Bloody well written ..

https://nyxt.atlas.engineer/article/elisp-vs-common-lisp.org

#nyxt #browser #elisp #clisp #opensource

Interesting. Git head of #Lisp HTML-generating library CL-WHO running on #Clisp :

[1]> (in-package "CL-WHO")
#<PACKAGE CL-WHO>
WHO[2]> (with-html-output-to-string (out) (:a (+ 1 2)))
"<a></a>"
WHO[3]> (with-html-output (*standard-output*) (:a (+ 1 2)))
<a></a>
"</a>"

No content in the tag!

Documentation says that the result of (+ 1 2) should be sent to the stream as if by PRINC, thus <a>2</a>.

I don't see a test for this.

Doesn't work in the oldest available git commit from 2009, either.

What u will c is 21 languages #ada #awk #bash #basic #C #clisp #C++ #COBOL #Forth #FORTRAN #go #java #lisp (mine) #lua #Pascal #Perl #Python #R #Rust #Ruby #SED calc app srvs <=>stdinout. C,C++<=> sockets, 23 thin clients /w NO dep. besides C #xcb #sockets. 21 thin server in C,translate stdin/out to/from sockets in a language agnostic way. What you WON'T see are any #browsers (1000x footprint of my thin clients) or fonts, ask for #retro computer clients https://www.youtube.com/watch?v=Esv6xHwZRYc

I feel old, can chatgpt write me some code to give #powershell the same ability to stdin/stdout that #ada, #awk, #bash, #basic, #c, #cpp, #cobol, #clisp, #go, #Forth, #Fortran, #java, #lisp, #lua, #pascal, #python, #perl, #r, #rust, #ruby, #SED all share? also if you know these langs I have tons of code u could shorten for me/us calc under https://bitbucket.org/timcdoc/antibrowser/src/master/

An unfair line comparison of #ada #awk #bash #basic #c #COBOL #clisp #Forth #FORTRAN #lisp #Pascal #Perl #Python #R #Rust (straight and with junk DNA removed using C pre processor, ya I don't know rust well) #Ruby #SED the ada c and lisp can be used as guides for optimizing if you know any of these. I'm slowly going back through now that these all work for calc https://bitbucket.org/timcdoc/antibrowser/src/master/ also note these all produce the same(mostly) tiny over the wire to thin client via stdin/out

This goes for the rest of you, if you can improve on the Rosetta stone 17 languages (and it won't be hard on most of them :-P ) feel free to send me a shorter/clearer version. https://bitbucket.org/timcdoc/antibrowser/src/master/ then #ada #awk #bash #basic #c #clisp #COBOL #Forth #FORTRAN #Pascal #Perl #Python #R #Rust #Sed (others but these are the easiest to grok under those dirs are calc and some other apps depending. What language should I abuse next?

TIL: every run of #SBCL has the same initial `*random-state*`, so sequences of pseudo-random numbers are not so random. The solution is super simple: `(setf *random-state* (make-random-state t))`.
It makes sense considering what a #Lisp image is... but it's still pretty surprising compared to other programming languages. (And doesn't happen in #ECL or #clisp 😅)

#CommonLisp

Where are my #clisp peeps? I suspect most lisps can do these kinds of self surgery on themselves, hopefully close to just as easily as the lisps I've written? Not the right way to write factorial, but hints at ways to write self compilers etc. I never did add macros, but I've never needed them.

#clisp mostly working #altair emulator runs 4K #BASIC but sin() is broken, should fix it today. 5717 bytes of human readable over the wire to a 252K footprint thin client with no fluffy dependencies. and no 300M footprint browser. Shown are all the commands including 5 RLE HRBitmaps over the thin client on the other end of the cloud/network. code on bitbucket timcdoc antibrowser clisp altair

@WorkWithKirk oh, I wouldn't even know how to chatgpt. I do have some pretty crappy mix of first (or near first language gui cloud apps) and used all the time languages #ada #awk #bash #BASIC #C #C++ #clisp #COBOL #Forth #FORTRAN #lisp (mine) #Pascal #perl #python and yes #SED implementations of calc, some paint, altair emulators under bitbucket timcdoc antibrowser if you know any of these I could use some optimization help. You can see runs to NOTbrowsers thin clients in my "media"

@bunnyhero you can see a calc 4 banger and an altair emulator in #clisp (probably horrible impl) and my lisp under bitbucket timcdoc antibrowser then lisp or clisp then calc or altair then calc.lsp or altair.lsp @WorkWithKirk [[Any clisp coders feel free to suggest ways to cut down the clisp code]]

I'm not saying this is the *right* way to write lisp code, but MY lisp handles this JUST fine, #clisp may or may not but you'd have to bend over backwards and disable the COBOL like anally retentive bumpers! 🤦 (Cackles maniacally, now I can haz nap!?) Why yes, this is like self brain surgery, hi, this is lisp! @bunnyhero @WorkWithKirk A good way to write factorial? maybe not, a good way to self optimize while running? ABSOLUTELY 😜🤜 @DRSpalding FYA

Another great practice with the Popes "only" two things, but lots of wood-shedding #Vanhal #doublebass concerto 1st,2nd,3rd movements, best ever? (low bar in the 3rd tho) #Mendelssohn #violin concerto Op 64 1st, 2nd and 3rd(short bridge thingy) thanks for counting in the solo scrambles! So for me that was #bass, violin, short nap, then back to work porting my #altair emulator #gui #cloud app from my #lisp to #clisp

I was yesterday years old when I discovered modern lisps ( #clisp ) can't directly manipulate their own functions from within their functions (de foo (x y) 'thisgetswhacked (rplacd (caddr foo) 'thisiswhatgetssmashedinto)) or that scoping was so effed up it should be and is in my lisps if a variable is used, and it's not in the variable list going into the function you are in, then it's global, otherwise it's in the scope of the function you are in.