Custom Query (1030 matches)

On at least some fairly recent versions of OSX, using drag-and-drop to drag text around in the Cocoa IDE generates an FP exception (invalid operation IIRC). This happens deep in some CG text-drawing code that's invoked by CCL calling the superclass's #/mouseDown: method, and we report it as an arithmetic error. The error's likely to just be confusing and disruptive to the user.

We can work around this particular bug by disabling FP exceptions around the next-method call.

We generally try to report FP exceptions that occur in foreign code; this certainly makes sense if (for instance) #_sin is called as part of the implementation of CL:SIN. It's less clear that it's desirable or useful to try to detect and report FP exceptions that have nothing to do with CL math functions, though we've traditionally done so.

Compiling a file with code such as following causes a full warning and a tertiary value of T from COMPILE-FILE.

(declaim (ftype (function () nil) arg-missing)) (defun arg-missing ()

(error "missing arg!"))

(defstruct foo

(bar (arg-missing)))

You can see a description of the problem and a solution at: ​http://common-lisp.net/pipermail/asdf-devel/2010-October/001708.html

A trace is shown at: ​http://paste.lisp.org/+2H95 [This paste will automatically go away in 6 days.]

In a nutshell, ASDF2 will unintern portions of itself if ASDF is already loaded and it is loaded again during the build process.

The solution is to start ccl with the --no-init option before invoking (ccl:rebuild-ccl :full t) so that any "(require :asdf)" form in .ccl-init is bypassed.

I don't think any code changes need be done to ccl, but it would be nice if something would be mentioned in the ccl documentation, otherwise this conflict between asdf and ccl is going to show up again.

Perhaps section "3.3 Building Everything" of the Clozure CL Documentation would be a good place to document this issue.