Custom Query (1030 matches)
Results (889 - 891 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #465 | fixed | Shorthand type declarations. | ||
| Description |
According to the <a href=""http://www.lispworks.com/reference/HyperSpec/Body/03_cca.htm">CLHS 3.3.3.1</a> type declarations can be shortened, but CCL gives a warning: (proclaim '((array character) *foo*)) ; Warning: Unknown declaration specifier(s) in ((ARRAY CHARACTER) *FOO*) |
|||
| #470 | fixed | Error when setting a value in a matrix unless safety 3 | ||
| Description |
Reported in http://clozure.com/pipermail/openmcl-devel/2009-May/009383.html. Test case: (defun test ()
(let ((array (make-array '(1 1) :initial-element 2.0
:element-type 'single-float))
(var 1.0))
(setf (aref array 0 0) var
var nil)))
|
|||
| #473 | fixed | ARGLIST-FROM-MAP confused by supplied-p variables | ||
| Description |
[I have a fix for this and will close this ticket as soon as I check it in; if I missed some case, we can re-open the ticket.] In the absence of better information, CCL:ARGLIST tries to construct a function's arglist from the function's symbol map (and lfun-bits.) Entries in the map generally appear in the reverse of the order in which variables come into scope, and supplied-p variables for optional args generally come into scope before subsequent optional args do; ARGLIST can't assume that ordered entries in the symbol map correspond to the names of arguments that can be passed by the caller unless we add some additional information or take some other steps to ensure this. (The "shape" of the argument list has been correct, but getting the names wrong can be confusing, especially since backtrace uses the same mechanism to identify arguments and other values.) |
|||
