From 8c9bca727c7ba25391e623c63280d50d81b08c68 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20=22phoe=22=20Herda?= Date: Fri, 15 Nov 2019 13:20:54 +0100 Subject: [PATCH] Comment out READ-SUPPRESS.17 Dispatch reader macros can consume arbitrary inputs, some of which might not be a valid Lisp expression. Following the discussion on #lisp, this commit comments out READ-SUPPRESS.17 under the premise that it is undefined what happens when an unknown dispatch reader macro is encountered under READ-SUPPRESS. --- reader/read-suppress.lsp | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/reader/read-suppress.lsp b/reader/read-suppress.lsp index 8960d36..86073f1 100644 --- a/reader/read-suppress.lsp +++ b/reader/read-suppress.lsp @@ -69,8 +69,9 @@ (def-random-suppress-test read-suppress.15 :prefix "#(" :suffix ")") (def-random-suppress-test read-suppress.16 :chars "0123456789.eEfFsSdDlL+-") -;; Undefined macro dispatch characters should not signal an error -(def-read-suppress-test read-suppress.17 "#garbage") +;; Undefined macro dispatch characters MAY signal an error - +;; the behaviour is undefined in this case +;; (def-read-suppress-test read-suppress.17 "#garbage") (def-read-suppress-test read-suppress.sharp-slash.1 "#\\boguscharname") (def-read-suppress-test read-suppress.sharp-slash.2 "#\\:x") -- GitLab