Custom Query (1030 matches)
Results (370 - 372 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1340 | fixed | apparent bug in UPGRADED-ARRAY-ELEMENT-TYPE | ||
| Description |
in the current trunk CCL (and likely earlier) pm x8664 ? (upgraded-array-element-type '(signed-byte 60)) FIXNUM ok. but ? (upgraded-array-element-type '(unsigned-byte 59)) (UNSIGNED-BYTE 64) does not seem to be ok I think that the problem is likely in the order in which CASE clauses are tested by CCL::CTYPE-SUBTYPE |
|||
| #1343 | notabug | incorrect results from read-line based on line ending format | ||
| Description |
example code attached. On windows Output of the read-line call is different depending on the line endings in the file, and currently only reading files with unix style line endings begets the appropriate behavior. A file rvs-prune.txt consisting of -d 30 -r m:\dump\ because nothing can ever be easy
with windows line endings read by the attached function produces
"-d 30 -r m: with mac "ecause nothing can ever be easy
with unix (expected output)
"-d 30 -r m: |
|||
| #1345 | moved | CCL 1.11-r16635 hangs after calling (quit) on Windows 8 or Windows 10 | ||
| Description |
I'm using Windows 8.1 and CCL 1.11-r16635 (wx86cl64.exe). When I start wx86cl64 and call (quit), the binary does not quit. It just hangs there with no further activity. ? (quit) I've tested this with the 64-bit binary and with the 32-bit binary. This issue does not happen all the time. With the 32-bit binary (wx86cl.exe) this hang does not occur as often as with the 64-bit binary. The 64-bit binary seems to hang on (quit) with a much higher likelihood on my windows. Windows 8.1 and Windows 10 seem to behave identical. In the windows taskmanager I see that the wx86cl64 binary changes from two thread to one thread when I call (quit). After this the application seems to hang on its last thread. Furthermore I've noticed that I can avoid the problem quite reliably when I change the compatibility setting of the wx86cl64.exe binary to Windows7. (This setting can be changed in the properties dialogue for the file wx86cl64.exe) I've seen that there is a similar ticket already: http://trac.clozure.com/ccl/ticket/1142 However I did not rebuild my lisp image and I don't see any error message at all (or at least I don't know where to look for an error message). If this is related to the same cause then just close this ticket. Any help on this is appreciated. |
|||
