Package: cl-named-readtables
Version: 20250524.git8bd0045-1
Severity: important
Tags: upstream patch

We noticed consfigurator was failing to build with recent SBCL, and I found a 
similar looking issue at

   https://github.com/atlas-engineer/nyxt/issues/3700

In particular the mentioned patch, unbreaks the
consfigurator build if applied to cl-named-readtables. Would you mind
either applying the patch or updating to a newer snapshot that
includes 6eea5667?

If needed I can do a team upload, but if you have time then it would
be great if you (Peter) can do it.

-- SYSTEM Information:
Debian Release: forky/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 6.17.9+deb14-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information
From: Gabor Melis <[email protected]>
Date: Sun, 9 Nov 2025 18:20:21 +0100
Subject: unbreak after SBCL internals change

(cherry picked from commit 6eea56674442b884a4fee6ede4c8aad63541aa5b)
---
 src/cruft.lisp | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/cruft.lisp b/src/cruft.lisp
index 01f9783..9b43cbd 100644
--- a/src/cruft.lisp
+++ b/src/cruft.lisp
@@ -231,7 +231,11 @@
                      (grovel-unicode-chars)
                      (let ((reader-fn (svref char-macro-array char-code))
                            (char (code-char (shiftf char-code (1+ 
char-code)))))
-                       (if reader-fn
+                       ;; In older SBCL, READER-FN may be NIL. Since
+                       ;; commit 00eabf5 ("Make a few mostly-stylistic
+                       ;; tweaks to macro char reading"), this is 0
+                       ;; instead.
+                       (if (and reader-fn (not (eql reader-fn 0)))
                            (yield char)
                            (grovel-base-chars)))))
                (grovel-unicode-chars ()

Reply via email to