Ignore:
Timestamp:
Oct 15, 2010, 3:15:03 AM (9 years ago)
Author:
gb
Message:

Admit that the macro CCL::REPORT-BAD-ARG has accepted exactly 2 arguments
for the last 20+ years. If the second argument (the typespec) is quoted,
warn at macroexpand time if it looks suspicious.

Fix a handful of cases that were detected by that change. In one
case, introduce a predicate so that EXPT can complain about an
argument whose realpart isn't positive via a SATISFIES type specifier.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/source/level-1/l1-streams.lisp

    r14255 r14365  
    64306430              (setf (fill-pointer displaced) newpos)))
    64316431          newpos)
    6432         (report-bad-arg newpos `(integer 0 `(,(- (the fixnum (io-buffer-limit outbuf)) origin)))))
     6432        (report-bad-arg newpos `(integer 0 (,(- (the fixnum (io-buffer-limit outbuf)) origin)))))
    64336433      (the fixnum (- (the fixnum (io-buffer-idx outbuf)) origin)))))
    64346434
     
    65856585          (setf (io-buffer-idx inbuf) (the fixnum (+ origin (the fixnum newpos))))
    65866586          newpos)
    6587         (report-bad-arg newpos `(integer 0 `(,(- (the fixnum (io-buffer-limit inbuf)) origin)))))
     6587        (report-bad-arg newpos `(integer 0 (,(- (the fixnum (io-buffer-limit inbuf)) origin)))))
    65886588      (the fixnum (- (the fixnum (io-buffer-idx inbuf)) origin)))))
    65896589
Note: See TracChangeset for help on using the changeset viewer.