Custom Query (1030 matches)
Results (796 - 798 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1241 | fixed | Apparent bug causes data mangling | ||
| Description |
https://lists.clozure.com/pipermail/openmcl-devel/2014-November/010720.html |
|||
| #1247 | fixed | socket timeout confusion | ||
| Description |
MAKE-SOCKET accepts timeout keyword arguments (:INPUT-TIMEOUT, :OUTPUT-TIMEOUT, and :CONNECT-TIMEOUT); non-null values of these arguments are supposed to be nonnegative REALs (according to the documentation) specifying time in seconds. ( Lower-level code (PROCESS-INPUT-WAIT, PROCESS-OUPUT-WAIT) takes optional timeout arguments which are required to be integers specifying time in milliseconds. MAKE-SOCKET seems to just pass its timeout arguments unmodified to the lower-level code. Wackiness ensues (in the formm of type-errors). See ticket:1242. I don't know whether this bug was newly introduced or if it's been present for a long time. |
|||
| #1282 | fixed | sertting a large number of macro characters doen't scale well | ||
| Description |
People have reported that it can be prohibitively slow to call SET-MACRO-CHARACTER on all potential Unicode characters. I'm not surprised by this, but I'm not sure that there's a good reason to make it impractical for someone who wants to do this to do so, either. changing the data structures that CCL uses to associate characters with functions can affect things like SET-SYNTAX-FROM-CHAR and COPY-READTABLE as well as SET-MACRO-CHARACTER and (poossibly) SET-DISPATCH-MACRO-CHARACTER. |
|||
