Custom Query (1030 matches)
Results (655 - 657 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #2 | fixed | DEF-FOREIGN-TYPE, "auxiliary" foreign types, side-effects | ||
| Description |
In trying to fix some issues related to how DEF-FOREIGN-TYPE and PARSE-FOREIGN-TYPE deal with "auxiliary" foreign types (e.g., record types), I've introduced a bug wherein some of the target-specific foreign types defined via INSTALL-STANDARD-FOREIGN-TYPES are only defined at compile-time. One symptom of this is that it isn't possible to compile "lib/db-io.lisp" unless "lib/foreign-types.lisp" has been compiled in the same session; in other words, the load-time effect of defining things like (:STRUCT :CDB-DATUM) doesn't take place. The whole concept of "auxiliary" foreign types is questionable, and the current foreign type system code applies it too broadly. Something like: (DEF-FOREIGN-TYPE NIL (:STRUCT FOO (:X :INT))) should always globally define or redefine the structure-type :FOO, and in something like: (DEF-FOREIGN-TYPE NIL (:STRUCT :BAR (:A (:STRUCT :FOO)))) the inner reference to (not definition of) (:STRUCT :FOO) should be a (possibly forward-) reference to the globally visible structure type :FOO. In a third case (should check a C reference), it is possible that in: (DEF-FOREIGN-TYPE NIL (:STRUCT :BAZ (:A (:STRUCT :FOO (:X :DOUBLE)))) the internal definition of (:STRUCT :FOO) is local to the containing definition, in which case the FOREIGN-RECORD-TYPE for :BAZ would need to enumerate all such local ("auxiliary") structure and type definitions. The old CMUCL type-system code (as it's been hacked up over the years) seems to want to treat all structure type definitions and references as if they were somehow local (to something ...), and attempting to fix this has introduced other problems. |
|||
| #4 | fixed | Problem loading additional frameworks in 070408 snapshot | ||
| Description |
Not sure if this is a bug or changes required on my end due to bridge changes re: framework loading as the error message isn't telling me anything helpful (I've attached the backtrace as Trac seems to want to wrap everything making it very difficult to read) |
|||
| #5 | fixed | Problem with new-pixel-format in examples | ||
| Description |
The macro new-pixel-format from the rubix opengl example code (in rubix/opengl.lisp) has been redefined as a function and does not appear to be functional. Error attached and here's the code which resulted in the error: (opengl:new-pixel-format #$NSOpenGLPFAMultisample
(it's a minor issue, but I do need the functionality as my non-example code uses it) |
|||
