Custom Query (1030 matches)
Results (979 - 981 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #743 | invalid | ccl::foreign-type-alignment returns incorrect alignment for :[un]signed-doubleword on x86 | ||
| Description |
Using 1.6-dev-r14265M-trunk (LinuxX8632):
The correct value is 32 |
|||
| #756 | invalid | read-line() broken for utf-16 and ucs-2 | ||
| Description |
I get a crash when executing something like (with-open-file (stream ucs-2-file :external-format :ucs-2) (print (read-line stream))) The same for :utf-16. read-char() is OK.
|
|||
| #763 | invalid | FP exception handling and "random" FP exceptions | ||
| Description |
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. |
|||
