Custom Query (1030 matches)
Results (970 - 972 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:| |
|||
| #1246 | fixed | Hemlock interns symbols indiscriminately | ||
| Description |
In the IDE: Welcome to Clozure Common Lisp Version 1.10-r16304M (DarwinX8664)! ? 'abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ ? (apropos 'abc) ABC ABCD ABCDE ABCDEF ABCDEFG ABCDEFGH ABCDEFGHI ABCDEFGHIJ ABCDEFGHIJK ABCDEFGHIJKL ABCDEFGHIJKLM ABCDEFGHIJKLMN ABCDEFGHIJKLMNO ABCDEFGHIJKLMNOP ABCDEFGHIJKLMNOPQ ABCDEFGHIJKLMNOPQR ABCDEFGHIJKLMNOPQRS ABCDEFGHIJKLMNOPQRST ABCDEFGHIJKLMNOPQRSTU ABCDEFGHIJKLMNOPQRSTUV ABCDEFGHIJKLMNOPQRSTUVW ABCDEFGHIJKLMNOPQRSTUVWX ABCDEFGHIJKLMNOPQRSTUVWXY ABCDEFGHIJKLMNOPQRSTUVWXYZ ABCDEFGHIJKLMNOPQRSTUVWZ :ABCL, Value: :ABCL ? |
|||
| #1256 | wontfix | Make HEAP-IVECTOR instances garbage-collectable | ||
| Description |
Since HEAP-IVECTOR instances are ignored by the GC, one has to wrap them in some other object to which a finalizer is attached, which is inconvenient. It would be better if HEAP-IVECTORs were automatically disposed while, at the same time, still allowing for manual disposal. |
|||
Note:
See TracQuery
for help on using queries.
