| commit | f41155df3e1d40d10b2eeafcbfc490733bbe4863 | |
| author | Alex Klinkhamer <grencez@gmail.com> | |
| Mon, 9 Jun 2008 00:19:30 +0000 (8 20:19 -0400) | ||
| committer | Alex Klinkhamer <grencez@gmail.com> | |
| Mon, 9 Jun 2008 00:19:30 +0000 (8 20:19 -0400) | ||
| tree | 19a62b83dd8ea3cceffc3e7c89ed696051250c73 | treesnapshot (tar.gz zip) |
| parent | 06aaefc6678dd6c6d93a256643d64bddac18ca74 | commitdiff |
Strange notes printing in crop functions
Having both of these lambda lists:
((u tuple) (n number))
((u mtrix) (n number))
for the crop and vcrop methods makes SBCL give a strange note the first
time a crop or vcrop is called. Taking 1 of the defmethods away for each
removes the mysterious output. Probably has something to do with order
of importance.
* ; in:
; LAMBDA (#:G2216 #:G2217 #:G2218 #:G2219 #:G2220 #:G2221 #:G2222
; #:G2223 #:G2224 #:G2225 #:G2226 #:G2227 ...)
; (TYPEP SB-PCL::.ARG1. 'INTEGER)
; --> INTEGERP
; ==>
; SB-PCL::.ARG1.
;
; note: deleting unreachable code
;
; compilation unit finished
; printed 1 note
Having both of these lambda lists:
((u tuple) (n number))
((u mtrix) (n number))
for the crop and vcrop methods makes SBCL give a strange note the first
time a crop or vcrop is called. Taking 1 of the defmethods away for each
removes the mysterious output. Probably has something to do with order
of importance.
* ; in:
; LAMBDA (#:G2216 #:G2217 #:G2218 #:G2219 #:G2220 #:G2221 #:G2222
; #:G2223 #:G2224 #:G2225 #:G2226 #:G2227 ...)
; (TYPEP SB-PCL::.ARG1. 'INTEGER)
; --> INTEGERP
; ==>
; SB-PCL::.ARG1.
;
; note: deleting unreachable code
;
; compilation unit finished
; printed 1 note
| src/overload/crop.lisp | diffblobblamehistory |