Custom Query (1030 matches)

The spec says that a warning should be issued if a variable declared to be ignored is declared SPECIAL, as in:

(defun foo (x y)
 (declare (ignore y))
 ...
 (locally
   (declare (special y))
   ...))

That code doesn't make much sense, but it clearly deservers a warning.

(defparameter y ...)

(defun foo (x y)
 (declare (ignore y))
 ...)

is about the same thing, but the warning in both cases should probably complain that inconsistent declarations applied to Y and not just say that it "wasn't IGNOREd".

It looks like some exception flags get left on in the MXCSR somehow.

/* fp.c -- compile with cc -shared fp.c -o fp.dylib */

double rme_fdiv(double x, double y)
{
    return x / y;
}

double rme_nan()
{
    return rme_fdiv(0.0, 0.0);
}

From lisp:

? (open-shared-library "/Users/rme/fp.dylib")
#<SHLIB /Users/rme/fp.dylib #x30200053443D>
? (external-call "rme_nan" :double-float)
1D+-0 #| not-a-number |#
? (log 1 2)
> Error: FLOATING-POINT-INVALID-OPERATION detected
>        performing LOG on (1.0)
> While executing: %FP-ERROR-FROM-STATUS, in process listener(1).
> Type :POP to abort, :R for a list of available restarts.
> Type :? for other options.
1 > :pop

? (log 1 2)
0.0
?

I'm not sure it's desirable to warn about JUNK being unused in the :around method below.

(defclass foo ()
  ())

(defmethod do-nothing ((f foo) junk)
  (or junk 42))

(defmethod do-nothing :around ((f foo) junk)
  (format t "~&hi")
  (format t "~&~s" (call-next-method))
  (format t "~&bye"))

;Compiler warnings :
;   In (DO-NOTHING :AROUND (FOO T)) inside an anonymous lambda form: Unused lexical variable JUNK