home.social

#commonlisp — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #commonlisp, aggregated by home.social.

fetched live
  1. The blog post below is about the values of
    (typep #(0 1 2) '(array integer))
    (typep #(0 1 2) '(array (signed-byte 16)))
    and similar.

    This matter _is_ actually detailed in the standard, but some careful reading is required.

    Also, note the differences and the subtype relationships between
    (array *)
    (array t)
    (array integer)
    (array (signed-byte 16))

    <simondobson.org/2026/08/07/str>

    #CommonLisp

  2. The blog post below is about the values of
    (typep #(0 1 2) '(array integer))
    (typep #(0 1 2) '(array (signed-byte 16)))
    and similar.

    This matter _is_ actually detailed in the standard, but some careful reading is required.

    Also, note the differences and the subtype relationships between
    (array *)
    (array t)
    (array integer)
    (array (signed-byte 16))

    <simondobson.org/2026/08/07/str>

    #CommonLisp

  3. Emacs Lisp has had bignums for quite a few years now (even though it got them much later than other lisps).

    See also `integer-length' and company.

    #CommonLisp
    #Elisp
    #Emacs
    #EmacsLisp

    @anthk

  4. Emacs Lisp has had bignums for quite a few years now (even though it got them much later than other lisps).

    See also `integer-length' and company.

    #CommonLisp
    #Elisp
    #Emacs
    #EmacsLisp

    @anthk

  5. 🎯 "Why write elegant poetry when you can just grunt in JavaScript?" wonders the author, who apparently prefers to vibe in a language so niche it requires a secret handshake to use. 😂 Clearly, targeting Common Lisp is the tech equivalent of choosing Latin for your blog posts—because who needs an audience? 🙄
    funcall.blogspot.com/2026/08/w #elegantpoetry #JavaScript #CommonLisp #nicheprogramming #techhumor #HackerNews #ngated

  6. 🎯 "Why write elegant poetry when you can just grunt in JavaScript?" wonders the author, who apparently prefers to vibe in a language so niche it requires a secret handshake to use. 😂 Clearly, targeting Common Lisp is the tech equivalent of choosing Latin for your blog posts—because who needs an audience? 🙄
    funcall.blogspot.com/2026/08/w #elegantpoetry #JavaScript #CommonLisp #nicheprogramming #techhumor #HackerNews #ngated

  7. As feared, there's something afoot with nested clipping using the stencil buffer. But we now have kittens (images).

    #McCLIM #SDL #CommonLisp #OpenGL #Lisp

  8. As feared, there's something afoot with nested clipping using the stencil buffer. But we now have kittens (images).

    #McCLIM #SDL #CommonLisp #OpenGL #Lisp

  9. There are still things that aren't working, like textures for patterns or complex clipping regions but, this has been illuminating where my opengl-fixed-function-medium isn't quite as reusable as I want it nicely.

    #CommonLisp #Lisp

  10. There are still things that aren't working, like textures for patterns or complex clipping regions but, this has been illuminating where my opengl-fixed-function-medium isn't quite as reusable as I want it nicely.

    #CommonLisp #Lisp

  11. I recently listened to an interesting podcast interview with Lua's creator. It got me thinking: Common Lisp, especially CMU CL and SBCL, offers impressive features like type inference. But who should they interview?

    #commonlisp

  12. I recently listened to an interesting podcast interview with Lua's creator. It got me thinking: Common Lisp, especially CMU CL and SBCL, offers impressive features like type inference. But who should they interview?

    #commonlisp

  13. I plan to stream #McCLIM dev things in about a 50 minutes, at 12pm CDT/17:00 UTC.

    twitch.tv/endparen

    I'm back at the problem of shoe-horning my #OpenGL fixed-function medium (renderer) into the alpha #SDL2 port

    #CommonLisp #Lisp

  14. I plan to stream #McCLIM dev things in about a 50 minutes, at 12pm CDT/17:00 UTC.

    twitch.tv/endparen

    I'm back at the problem of shoe-horning my #OpenGL fixed-function medium (renderer) into the alpha #SDL2 port

    #CommonLisp #Lisp

  15. I've converted many of the GLUT keyboard shortcuts I had to CLIM frame commands. Unless I'm missing something, I had to implement them in the more traditional GUI sense rather than being able to use CLIM gestures which I was hoping for.

    It's been a fun exercise so far, but I'm going to pause on the conversion and experiment with ways to make the "gl-pane" as a clim-stream / presentation.

    #McCLIM #CommonLisp #OpenGL #Lisp

  16. I've converted many of the GLUT keyboard shortcuts I had to CLIM frame commands. Unless I'm missing something, I had to implement them in the more traditional GUI sense rather than being able to use CLIM gestures which I was hoping for.

    It's been a fun exercise so far, but I'm going to pause on the conversion and experiment with ways to make the "gl-pane" as a clim-stream / presentation.

    #McCLIM #CommonLisp #OpenGL #Lisp

  17. i like parser combinators because writing it feels like expressing a DCG/BNF/smth

    #commonlisp #haskell

  18. i like parser combinators because writing it feels like expressing a DCG/BNF/smth

    #commonlisp #haskell

  19. ...And after a couple more GL state fixes we have the 3D view rendering well with the interactor pane.

    #McCLIM #OpenGL #CommonLisp

  20. ...And after a couple more GL state fixes we have the 3D view rendering well with the interactor pane.

    #McCLIM #OpenGL #CommonLisp

  21. With a few tweaks after I ended stream yesterday, we are much closer. The main difference is switching to make the `gl-window` pane a `gadget` instead of an `application-pane`...And also fixing the Y-flip.

    The interactor pane is now not rendering well, so I need to track that down but otherwise I'm about ready to try converting mouse and keyboard input.

    #McCLIM #CommonLisp #OpenGL #Lisp

  22. With a few tweaks after I ended stream yesterday, we are much closer. The main difference is switching to make the `gl-window` pane a `gadget` instead of an `application-pane`...And also fixing the Y-flip.

    The interactor pane is now not rendering well, so I need to track that down but otherwise I'm about ready to try converting mouse and keyboard input.

    #McCLIM #CommonLisp #OpenGL #Lisp

  23. Yes, this is an important feature¹.

    Another benefit is that consuming some kinds of non-Lisp data is very easy to implement with reader macros.
    As a quick example, reading assumed-to-be-valid JSON (at least in a good majority of cases) only needs one simple and five trivial macros.
    (The ones for open brace and open bracket would use `read-delimited-list', of course.)

    _________
    ¹ Redundant to add, one should know what one is doing, naturally (for sharpsign-dot this includes assigning the correct value to `*read-eval*').

    #CommonLisp

    @pascal_costanza @simon_brooke @screwlisp @ramin_hal9001 @D

  24. Yes, this is an important feature¹.

    Another benefit is that consuming some kinds of non-Lisp data is very easy to implement with reader macros.
    As a quick example, reading assumed-to-be-valid JSON (at least in a good majority of cases) only needs one simple and five trivial macros.
    (The ones for open brace and open bracket would use `read-delimited-list', of course.)

    _________
    ¹ Redundant to add, one should know what one is doing, naturally (for sharpsign-dot this includes assigning the correct value to `*read-eval*').

    #CommonLisp

    @pascal_costanza @simon_brooke @screwlisp @ramin_hal9001 @D

  25. Elia offers advice on picking a Lisp language to learn and presents the most relevant ones in active use: CommonLisp, Clojure, and Racket.

    scotto.me/blog/2026-07-17-whic

    #CommonLisp #Clojure #scheme #lisp

  26. Elia offers advice on picking a Lisp language to learn and presents the most relevant ones in active use: CommonLisp, Clojure, and Racket.

    scotto.me/blog/2026-07-17-whic

    #CommonLisp #Clojure #scheme #lisp

  27. «except, of course, for #CommonLisp which is a complete baroque mess.»

    This is a big exaggeration.

    «`#$(words)`»

    This is not standard Common Lisp.

    @simon_brooke @screwlisp @ramin_hal9001 @D

  28. «except, of course, for #CommonLisp which is a complete baroque mess.»

    This is a big exaggeration.

    «`#$(words)`»

    This is not standard Common Lisp.

    @simon_brooke @screwlisp @ramin_hal9001 @D

  29. @screwlisp @ramin_hal9001 "The great thing about #Lisp is that it has extremely simple syntax"

    ... except, of course, for #CommonLisp which is a complete baroque mess.

    Of course, it's largely a complete baroque mess because reader macros, and reader macros are useful shorthand, but `#$(words)`? Really?

    And noted also that #Clojure has its own baroquery hard-coded into its reader (`#{:a :b [:c @D]}`, anyone?), which is arguably worse, but...

    This might as well be #Perl.

  30. @screwlisp @ramin_hal9001 "The great thing about #Lisp is that it has extremely simple syntax"

    ... except, of course, for #CommonLisp which is a complete baroque mess.

    Of course, it's largely a complete baroque mess because reader macros, and reader macros are useful shorthand, but `#$(words)`? Really?

    And noted also that #Clojure has its own baroquery hard-coded into its reader (`#{:a :b [:c @D]}`, anyone?), which is arguably worse, but...

    This might as well be #Perl.

  31. Planning on streaming #McCLIM gui dev in an hour, at 11:30a CDT / 16:30 UTC.

    twitch.tv/endparen

    I wrote a semi-functional OBJ viewer when I first started learning Common Lisp and #OpenGL nearly 20 years ago. The code isn't pretty but it uses GLUT. I want to experiment changing it to a McCLIM app, keeping most of warts as-is -- just the minimum to replace GLUT.

    #CommonLisp #Lisp

  32. Planning on streaming #McCLIM gui dev in an hour, at 11:30a CDT / 16:30 UTC.

    twitch.tv/endparen

    I wrote a semi-functional OBJ viewer when I first started learning Common Lisp and #OpenGL nearly 20 years ago. The code isn't pretty but it uses GLUT. I want to experiment changing it to a McCLIM app, keeping most of warts as-is -- just the minimum to replace GLUT.

    #CommonLisp #Lisp

  33. common lisp quick reference
    clqr.boundp.org/

    it'd be magnificent if this could be brought into the slime/sly documentation system somehow. existing docs leave much to be desired: overcomplicated details combined with lacking docstrings for basic functions.

    #commonLisp #lisp

  34. common lisp quick reference
    clqr.boundp.org/

    it'd be magnificent if this could be brought into the slime/sly documentation system somehow. existing docs leave much to be desired: overcomplicated details combined with lacking docstrings for basic functions.

    #commonLisp #lisp

  35. As a first approximation, I suggest thinking of Emacs Lisp as closer to MacLisp than to Common Lisp.

    A precise description of "closer" would be fairly long.
    For example, Emacs Lisp acquired things like bignums and lexical bindings fairly late.

    Again as an approximation, the descendancies are:
    MacLisp → Emacs Lisp
    MacLisp and others → Common Lisp
    (Those others include, in alphabetical order, Interlisp, Scheme, Zeta Lisp, etc., but not Emacs Lisp.)

    And then an important aspect of these approximations is the `cl' package, also a late addition that evolved quite a bit.

    Transferring knowledge about C to Emacs Lisp is rather tricky, even though the implementation of a part of Emacs (including the Emacs Lisp virtual machine) is written in C.

    #CommonLisp
    #Elisp
    #Emacs
    #EmacsLisp

    @me

  36. As a first approximation, I suggest thinking of Emacs Lisp as closer to MacLisp than to Common Lisp.

    A precise description of "closer" would be fairly long.
    For example, Emacs Lisp acquired things like bignums and lexical bindings fairly late.

    Again as an approximation, the descendancies are:
    MacLisp → Emacs Lisp
    MacLisp and others → Common Lisp
    (Those others include, in alphabetical order, Interlisp, Scheme, Zeta Lisp, etc., but not Emacs Lisp.)

    And then an important aspect of these approximations is the `cl' package, also a late addition that evolved quite a bit.

    Transferring knowledge about C to Emacs Lisp is rather tricky, even though the implementation of a part of Emacs (including the Emacs Lisp virtual machine) is written in C.

    #CommonLisp
    #Elisp
    #Emacs
    #EmacsLisp

    @me

  37. RE: cosocial.ca/@robpike/117022640

    Put In Seven Extremely Random User Interface Commands.

    (See the second edition about what ruined that.)

    #CommonLisp

  38. RE: cosocial.ca/@robpike/117022640

    Put In Seven Extremely Random User Interface Commands.

    (See the second edition about what ruined that.)

    #CommonLisp

  39. Just spent a day and a half hunting down a bug that was making me question my sanity. As it turns out, #emacs #lisp's / function silently drops the decimal in its result if both of its inputs are integers... so (/ 1 2) evaluates to 0, not 0.5. Granted, this is also the way that C does it, but in my defense, #CommonLisp does not do this.