Custom Query (1030 matches)
Results (577 - 579 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1244 | invalid | ObjC bridge interface weirdness | ||
| Description |
Welcome to Clozure Common Lisp Version 1.10-r16303M (DarwinX8664)! ? (objc:load-framework "Quartz" :quartz) NIL ? #'#/pageAtIndex: > Error: Undefined function: NEXTSTEP-FUNCTIONS:|pageAtIndex:| > While executing: CCL::%FUNCTION, in process Listener(4). > Type cmd-. to abort, cmd-\ for a list of available restarts. > Type :? for other options. 1 > This problem is reliably repeatable, but it has randomly and mysteriously appeared and disappeared in different versions. For example, it was working in r16302: Welcome to Clozure Common Lisp Version 1.10-r16302M (DarwinX8664)! ? (objc:load-framework "Quartz" :quartz) NIL ? #'#/pageAtIndex: #<OBJC-DISPATCH-FUNCTION NEXTSTEP-FUNCTIONS:|pageAtIndex:| #x3020015710CF> ? and r16286: Welcome to Clozure Common Lisp Version 1.9-r16286M (DarwinX8664)! ? (objc:load-framework "Quartz" :quartz) NIL ? #'#/pageAtIndex: #<OBJC-DISPATCH-FUNCTION NEXTSTEP-FUNCTIONS:|pageAtIndex:| #x30200144C34F> But broken in r16266: Welcome to Clozure Common Lisp Version 1.10-store-r16266 (DarwinX8664)! ? (objc:load-framework "Quartz" :quartz) NIL ? #'#/pageAtIndex: Error: Undefined function: NEXTSTEP-FUNCTIONS:|pageAtIndex:| |
|||
| #1252 | fixed | OSX udp socket, "Socket is already connected (error #56) during sendto" | ||
| Description |
on osx 10.7.5. when attempting to call send-to on a socket that already has remote-port/host or local-port set, ccl reports "socket is already connected (error #56) during send-to" code example to tickle this problem http://paste.lisp.org/display/144678 after evaluating the defparameters calls to create the test vector and the socket, all three of the send-to calls fail with the same problem Similar problems are encountered in python apparently. see https://github.com/zerovm/zerocloud/issues/86 |
|||
| #838 | fixed | Null characters confuse Hemlock | ||
| Description |
A #\null character in a lisp file causes the remainder of the file (after the #\Null) to quietly not appear if you open such a file in Hemlock in the Cocoa IDE. If you then save this file, the file gets truncated after the #\null character. Leaving aside the issue of how such a character would find its way into a Lisp file in the first place, this is certainly poor behavior on the part of the editor. Other utilities in the IDE (like the Search Files grepper) don't seem to have a problem with #\null characters in files. |
|||
