Custom Query (1030 matches)

Welcome to Clozure Common Lisp Version 1.8  (LinuxX8632)!
? (deftype foo () '(complex double-float))
FOO
? (coerce #c(2 4) '(complex double-float))
#C(2.0D0 4.0D0)
? (coerce #c(2 4) 'foo)
> Error: value #C(2 4) is not of the expected type REAL.
> While executing: COMPLEX, in process listener(1).
> Type :POP to abort, :R for a list of available restarts.
> Type :? for other options.
1 > 

Basically this happens because coerce-to-complex works on the literal type specifier instead of the canonicalized ctype. I've included a small patch to remedy this.

The following sequence of events produces a memory fault and a trip to a nonfunctioning debugger.

(load "jpeg.lisp") ;supplied (jpeg::read-file "128.jpg") ;also supplied

If you wrap the latter in ignore-errors, you still get the trip to the debugger.

I tried this in the windows 32 bit 1.5 release as well as in the linux x86 64bit trunk (checked out as of this morning).

From the test suite:

(EXP (+ (LOG MOST-POSITIVE-SINGLE-FLOAT) 100))
(EXP (+ (LOG MOST-POSITIVE-DOUBLE-FLOAT) 100))

Both should signal floating-point-overflow, but instead return "1E++0" and "2E++0"