#commonlisp

This port of the CL condition system to Jolt looks interesting. Haven't been through it in detail, but the write-up on it, at a quick glance, looks thorough. https://reddit.com/r/Clojure/comments/1wr299y/cl_conditions_and_restarts_in_jolt/ (I don't know what Jolt is either, but I guess a Clojure library or DSL. since it's on their subreddit.) EDIT: I see the Foralero package, which I did not look up because the name did not immediately suggest conditions, is probably the real source. I'm not a Clojure user so just stumbled into this by chance. https://github.com/IGJoshua/farolero #CommonLisp #lisp #ConditionHandling #ErrorHandling #ErrorSystem #clojure

«As for Common Lisp: we forgot where [`dpb'] came from but we think we inherited some random characters from 60+ years ago.» We also have setf places (and immutable numbers). #CommonLisp @larsbrinkhoff@mastodon.sdf.org @amszmidt@mastodon.social @Ardubal@mastodon.xyz

@screwlisp@gamerplus.org @ramin_hal9001@fe.disroot.org "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@mastodon.scot]}, anyone?), which is arguably worse, but...

This might as well be #Perl.

«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@mastodon.scot @screwlisp@gamerplus.org @ramin_hal9001@fe.disroot.org @D@mastodon.scot

Unified power-user environment and knowledge-representation in Common Lisp https://project-mage.org/ #HackerNews #Tech #CommonLisp

The TMode Lisp library is interesting for both its features and its design approach. TMode is a library for creating text-mode user interfaces in Common Lisp. [...] By design it is a zero-dependency library, no ncurses, cffi or anything required. https://codeberg.org/fourier/cl-tmode #CommonLisp #lisp #TUI

On the subject of `common-lisp:loop’, I offer an exercise at the intermediate level (or maybe a little more than intermediate).

How would you implement a `for’ subclause extending the loop facility with a way to step through a sequence (of the generic kind, i.e. a single subclause that works for both lists and vectors)? Would adding such a subclause be a good idea or not, and why?

#CommonLisp

Let me add several notes (but no spoilers): One part of the exercise is designing an approach to process sequences generically that can work with the Loop Facility. Dave Tenny's post upthread describes one possibility. Another part is in working out how to extend the Loop Facility itself so one can say (loop for x some-sequence ...) where coming up with a suitable keyword for the placeholder is a subpart of the exercise. Yet another part is thinking about the trade-offs involved in introducing such a subclause. This includes understanding how hardware and compiler technologies have changed in about half a century since the Loop Facility was first designed, so reasonable trade-offs have also changed. And a metanote repeating the well-known: the value of such exercises is in _doing_ them, not in obtaining the final result. #CommonLisp #ComputerProgramming #Lisp #ProgrammingLanguageDesign @davetenny@hachyderm.io

I'm pleased to announce that I managed to get the draft Common Lisp Specification translated from TeX to an s-expression based document format. I started this project in 2015 and finally finished it this year (maybe a bit late for it to be relevant). The HTML proof-of-concept is at metaspec.dev/ and is probably the most complete rendering of the spec to date. It contains the acknowledgements, the appendix, errata, and preserves editorial TeX comments in the margins. It uses a patching system against sdoc to make auditable corrections and MathML to render the TeX mathy bits. The code that generates it, and a copy of the metaspec.sdoc file can be found at codeberg.org/dlowe/metaspectre #CommonLisp #Lisp #TeX

@screwlisp@gamerplus.org @kentpitman@climatejustice.social I’m just reading up on the MIT-Scheme condition system. Recent efforts to standardize this are defined in SRFI-255: “Restarting conditions”. An older standards condition systems in Scheme was defined in SRFI-35: “Conditions”. And #Guile users can use the Guile implementation of SRFI-35 to make use of it. I wish I had known about this two weeks ago when we first started talking about it on the #LispyGopherClimate show, but better late than never, I guess. #tech #software #Lisp #CommonLisp #Scheme #SchemeLang #R7RS #MITScheme #Guile #GuileScheme

@momo@woof.tech cool! Well then, please have a listen to the episodes of the #LispyGopherClimate podcast that me, @kentpitman@climatejustice.social and @screwlisp@gamerplus.org did these past few weeks: Kent Pitman presents his lisp condition system implemented for pythonKent Pitman, Scott Zimmermann, Ramin Honary, Screwlisp: Lisp Conditions in PythonKent Pitman with Common Lisp condition handling loreKent Pitman, Common Lisp condition system, code review of my programming exampleCommon Lisp condition handling w/ Kent Pitman, Ramin Honary #tech #software #Lisp #CommonLisp #Scheme #SchemeLang #R7RS #MITScheme #Guile #GuileScheme