From bbc517aca1bb7e9fd80e3b98e69e74154045fb4d Mon Sep 17 00:00:00 2001 From: pfdietz <pfdietz@localhost> Date: Wed, 26 Feb 2003 10:07:55 +0000 Subject: [PATCH] It was pointed out to me that the 'should be prepared' terminology for error checking applied to the case where the first argument of map-into is NIL. In that case, it's an extra step to check whether the other arguments are sequences, so 'lazy' checking can skip it. Modified test map-into.error.2 to accept either outcome. --- ansi-tests/map-into.lsp | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/ansi-tests/map-into.lsp b/ansi-tests/map-into.lsp index 53e034b8..cc0c1f42 100644 --- a/ansi-tests/map-into.lsp +++ b/ansi-tests/map-into.lsp @@ -351,9 +351,15 @@ (classify-error (map-into 'a #'(lambda () nil))) type-error) +;;; The next test was changed because if the first argument +;;; is NIL, map-into is said to 'return nil immediately', so +;;; the 'should be prepared' notation for the error checking +;;; means that error checking may be skipped. (deftest map-into.error.2 - (classify-error (map-into nil #'identity 'a)) - type-error) + (case (classify-error (map-into nil #'identity 'a)) + ((nil type-error) 'good) + (t 'bad)) + good) (deftest map-into.error.3 (classify-error (map-into (copy-seq '(a b c)) #'cons '(d e f) 100)) -- GitLab