Custom Query (1030 matches)
Results (175 - 177 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1186 | fixed | FORMAT prints one digit too many after decimal point for ~e directive | ||
| Description |
FORMAT prints one digit too many after decimal point for ~e directive (CLHS 22.3.3.2). E.g.: $ ./lx86cl Welcome to Clozure Common Lisp Version 1.9-r16078 (LinuxX8632)! ? (loop for d in '(1 2 3 4 5 6) do (format t "~,ve ~,ve~%" d 1.2345678e-10 d 1.2345678e+10)) 1.23E-10 1.23E+10 1.235E-10 1.235E+10 1.2346E-10 1.2346E+10 1.23457E-10 1.23457E+10 1.234568E-10 1.234568E+10 1.2345679E-10 1.2345678E+10 NIL On the other hand SBCL 1.0.55.0 is correct from what I can tell: * (loop for d in '(1 2 3 4 5 6) do (format t "~,ve ~,ve~%" d 1.2345678e-10 d 1.2345678e+10)) 1.2e-10 1.2e+10 1.23e-10 1.23e+10 1.235e-10 1.235e+10 1.2346e-10 1.2346e+10 1.23457e-10 1.23457e+10 1.234568e-10 1.234568e+10 NIL |
|||
| #671 | invalid | INTEGER-DECODE-FLOAT not consistent with DECODE-FLOAT | ||
| Description |
I get the following return values from INTEGER-DECODE-FLOAT. (Version 1.4-r13122 (WindowsX8632)) ? (integer-decode-float 0s0) 0 -150 1 ? (integer-decode-float 0f0) 0 -150 1 ? (integer-decode-float 0d0) 0 -1074 1 ? (integer-decode-float 0l0) 0 -1074 1 In contrast: ? (decode-float 0s0) 0.0 0 1.0 ? (decode-float 0f0) 0.0 0 1.0 ? (decode-float 0d0) 0.0D0 0 1.0D0 ? (decode-float 0l0) 0.0D0 0 1.0D0 CLHS states that INTEGER-DECODE-FLOAT returns "the same last two values that are returned by decode-float". Observed behavior seems otherwise. |
|||
| #16 | fixed | extraneous "6" in x862.lisp | ||
| Description |
There's an extraneous "6" on line 18 of ccl:compiler;X86;x862.lisp |
|||
Note:
See TracQuery
for help on using queries.
