Greetings!
I realize that this is not a sensible thing to do, but is this expected behaviour?
Thanks for the nifty system,
Robert
==========
In Slime:
; SLIME 2.26.1 CL-USER> (defmethod print-object ((obj string) s) (format s ""foo"")) foofoo CL-USER> 'foo foofoo CL-USER> 22 foofoo CL-USER>
========== In the shell:
alecto$ sbcl This is SBCL 2.0.1.openbsd, an implementation of ANSI Common Lisp. More information about SBCL is available at http://www.sbcl.org/.
SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * (defmethod print-object ((obj string) s) (format s ""foo"")) #<STANDARD-METHOD COMMON-LISP:PRINT-OBJECT (STRING T) {10020C01C3}> * "xxx" "foo" * 'foo FOO * 22 22
========== I am using:
(progn (load "/home/<name>/quicklisp/dists/quicklisp/software/slime-v2.26.1/swank-loader.lisp" :verbose t) (funcall (read-from-string "swank-loader:init") :from-emacs t) (funcall (read-from-string "swank:start-server") "/tmp/slime.81676"))
This is SBCL 2.0.1.openbsd, an implementation of ANSI Common Lisp. More information about SBCL is available at http://www.sbcl.org/.
SBCL is free software, provided as is, with absolutely no warranty. It is mostly in the public domain; some portions are provided under BSD-style licenses. See the CREDITS and COPYING files in the distribution for more information. * ; loading #P"/home/<name>/quicklisp/dists/quicklisp/software/slime-v2.26.1/swank-loader.lisp" WARNING: redefining EMACS-INSPECT (#<SB-PCL:SYSTEM-CLASS COMMON-LISP:T>) in DEFMETHOD ;; Swank started at port: 6421. 6421 * WARNING: redefining SWANK::SYMBOL-INDENTATION in DEFUN WARNING: redefining SWANK::MACRO-INDENTATION in DEFUN WARNING: redefining THREAD-FOR-EVALUATION (#<STRUCTURE-CLASS SWANK::MULTITHREADED-CONNECTION> #<SB-MOP:EQL-SPECIALIZER :FIND-EXISTING>) in DEFMETHOD
On Mon, 12 Jul 2021 at 02:36, Robert Krug destiny6@mac.com wrote:
I realize that this is not a sensible thing to do, but is this expected behaviour?
It doesn't seem totally unexpected, though perhaps there's some PRINTing going on that could be replaced with WRITE-STRING.
Cheers,