0.8.11.6:

[sbcl.git] / tests / pprint.impure.lisp

diff --git a/tests/pprint.impure.lisp b/tests/pprint.impure.lisp
index ee1f91a..66efdc1 100644 (file)
--- a/tests/pprint.impure.lisp
+++ b/tests/pprint.impure.lisp
@@ -88,6 +88,81 @@
                               ;2~%~
                               ;3x"))))
 
+;;; bug 141b: not enough care taken to disambiguate ,.FOO and ,@FOO
+;;; from , .FOO and , @FOO
+(assert (equal
+        (with-output-to-string (s)
+          (write '`(,  .foo) :stream s :pretty t :readably t))
+        "`(, .FOO)"))
+(assert (equal
+        (with-output-to-string (s)
+          (write '`(,  @foo) :stream s :pretty t :readably t))
+        "`(, @FOO)"))
+(assert (equal
+        (with-output-to-string (s)
+          (write '`(,  ?foo) :stream s :pretty t :readably t))
+        "`(,?FOO)"))
 
+;;; bug reported by Paul Dietz on sbcl-devel: unquoted lambda lists
+;;; were leaking the SB-IMPL::BACKQ-COMMA implementation.
+(assert (equal
+        (with-output-to-string (s)
+          (write '`(foo ,x) :stream s :pretty t :readably t))
+        "`(FOO ,X)"))
+(assert (equal
+        (with-output-to-string (s)
+          (write '`(foo ,@x) :stream s :pretty t :readably t))
+        "`(FOO ,@X)"))
+#+nil ; '`(foo ,.x) => '`(foo ,@x) apparently. 
+(assert (equal
+        (with-output-to-string (s)
+          (write '`(foo ,.x) :stream s :pretty t :readably t))
+        "`(FOO ,.X)"))
+(assert (equal
+        (with-output-to-string (s)
+          (write '`(lambda ,x) :stream s :pretty t :readably t))
+        "`(LAMBDA ,X)"))
+(assert (equal
+        (with-output-to-string (s)
+          (write '`(lambda ,@x) :stream s :pretty t :readably t))
+        "`(LAMBDA ,@X)"))
+#+nil ; see above
+(assert (equal
+        (with-output-to-string (s)
+          (write '`(lambda ,.x) :stream s :pretty t :readably t))
+        "`(LAMBDA ,.X)"))
+(assert (equal
+        (with-output-to-string (s)
+          (write '`(lambda (,x)) :stream s :pretty t :readably t))
+        "`(LAMBDA (,X))"))
+;;; more backquote printing brokenness, fixed quasi-randomly by CSR.
+;;; NOTE KLUDGE FIXME: because our backquote optimizes at read-time,
+;;; these assertions, like the ones above, are fragile.  Likewise, it
+;;; is very possible that at some point READABLY printing backquote
+;;; expressions will have to change to printing the low-level conses,
+;;; since the magical symbols are accessible though (car '`(,foo)) and
+;;; friends.  HATE HATE HATE.  -- CSR, 2004-06-10
+(assert (equal
+        (with-output-to-string (s)
+          (write '``(foo ,@',@bar) :stream s :pretty t))
+        "``(FOO ,@',@BAR)"))
+(assert (equal
+        (with-output-to-string (s)
+          (write '``(,,foo ,',foo foo) :stream s :pretty t))
+        "``(,,FOO ,',FOO FOO)"))
+(assert (equal
+        (with-output-to-string (s)
+          (write '``(((,,foo) ,',foo) foo) :stream s :pretty t))
+        "``(((,,FOO) ,',FOO) FOO)"))
+\f
+;;; SET-PPRINT-DISPATCH should accept function name arguments, and not
+;;; rush to coerce them to functions.
+(set-pprint-dispatch '(cons (eql frob)) 'ppd-function-name)
+(defun ppd-function-name (s o)
+  (print (length o) s))
+(let ((s (with-output-to-string (s)
+          (pprint '(frob a b) s))))
+  (assert (position #\3 s)))
+\f
 ;;; success
 (quit :unix-status 104)