Custom Query (1030 matches)
Results (127 - 129 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #563 | fixed | possible bug in format tilde e | ||
| Description |
When I do (setq x 0) (loop (setq x (+ x .00001)) (format t "~%~8,2e" x)) I pretty soon see lines of varying width such as
and I wonder if that can be right. From the ANSI:
|
|||
| #1358 | duplicate | possible bug in LOOP | ||
| Description |
see <https://lists.clozure.com/pipermail/openmcl-devel/2016-April/011247.html> |
|||
| #938 | fixed | please not SIMPLE-ERROR | ||
| Description |
Mark Nahabedian 2010-05-24 09:33:02 EDT There are a variety of cases where CCL signals nothing more specific than SIMPLE-ERROR. It would be helpful if appropriate conditions were defined for each of these cases and those conditions were signaled. Here's an example of a case of SIMPLE-ERROR that should be something like NO-APPLICABLE-METHOD-ERROR instead: There is no applicable method for the generic function: #<STANDARD-GENERIC-FUNCTION QRES-CORE:DO-LOAD-DB-RECORD-FROM-QAPI-OBJECT #x3000434D4C2F> when called with arguments: (QRES-CORE:QAPI-PNR-SEGMENT NIL :PARENTS (#<QAPI-PNR #<LEGACY-PNR 12474990031128/M/0 AC:PZCCLE,AC:PZCCLE #x300062B32F8D> :CHANGE-TOKEN: NIL>)) NB: Was ITA bug 80692 |
|||
