Custom Query (1030 matches)

This function is documented as accepting any ivector. However the actual behavior is quite different:

? (defvar arr (make-array 5 :element-type 'single-float))
ARR
? (with-open-file (s "/dev/zero" :direction :input :element-type '(unsigned-byte 8))
    (stream-read-ivector s arr 0 20))
> Error: 0 doesn't match array element type of #<VECTOR 5 type SINGLE-FLOAT, simple>.
> While executing: CCL::%IOBLOCK-BINARY-IN-IVECT, in process listener(1).

This is fixed by the following change, but it is obviously a very ugly hack that depends on the implementation details of the read function:

--- l1-streams.lisp     (revision 13365)                           
+++ l1-streams.lisp     (working copy)                             
@@ -2471,10 +2471,10 @@                                            
     (let* ((b (funcall rbf ioblock)))                             
       (if (eq b :eof)                                             
        (return (- i start)))                                      
-      (setf (uvref vector i) b)                                   
-      (incf i)                                                    
-      (decf need)                                                 
-      (let* ((idx (io-buffer-idx in))                             
+   ;   (setf (uvref vector i) b)                                  
+   ;   (incf i)                                                   
+   ;   (decf need)                                                
+      (let* ((idx (1- (io-buffer-idx in)))                        
             (count (io-buffer-count in))                          
             (avail (- count idx)))                                
        (declare (fixnum idx count avail))

testing attachments

Calling WARN messes with the pretty-printer.

CL-USER> (lisp-implementation-version)
"Version 1.4-RC1-r13031  (LinuxX8632)"
CL-USER> (setq *print-pretty* t)
T

CL-USER> (format t "~@<COMPILE-FILE failed while performing ~A on ~A.~@:>"
                 "#<COMPILE-OP (:FORCE T) #x150A26AE>" 
                 "#<IRONCLAD-SOURCE-FILE \"ripemd-160\" #x14D18B46>")
COMPILE-FILE failed while performing #<COMPILE-OP (:FORCE T) #x150A26AE> on
#<IRONCLAD-SOURCE-FILE "ripemd-160" #x14D18B46>.
NIL

CL-USER> (warn "~@<COMPILE-FILE failed while performing ~A on ~A.~@:>"
              "#<COMPILE-OP (:FORCE T) #x150A26AE>"
               "#<IRONCLAD-SOURCE-FILE \"ripemd-160\" #x14D18B46>")
; Warning: COMPILE-FILE failed while performing
;                     #<COMPILE-OP (:FORCE T) #x150A26AE> on
;                     #<IRONCLAD-SOURCE-FILE "ripemd-160" #x14D18B46>.
; While executing: SWANK::EVAL-REGION, in process repl-thread(11).
NIL

As you can see, WARN somehow messes with pretty-printing.