Custom Query (1030 matches)
Results (232 - 234 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #475 | fixed | startup chokes when ccl directory path contains non-ascii chars | ||
| Description |
(from http://clozure.com/pipermail/openmcl-devel/2009-May/009380.html) In cmd.exe, I cd to c:\cclㅁ; (c:\cclM where M is the square Korean character #\u+3141; any Korean characters in the path have this effect) and run C:\cclㅁ>wx86cl.exe > log.txt > Error: value NIL is not of the expected type (OR STRING PATHNAME STREAM). > While executing: PATHNAME-DIRECTORY, in process Initial(0). > Type :GO to continue, :POP to abort, :R for a list of available restarts. > If continued: Skip (possibly crucial) startup function CCL::INIT-LOGICAL-DIRECTORIES. > Type :? for other options. > Error: value NIL is not of the expected type CCL::RECURSIVE-LOCK. > While executing: CCL::RECURSIVE-LOCK-PTR, in process Initial(0). > Type :POP to abort, :R for a list of available restarts. We see a similar problem on Darwin: $ cd ccl-1.3-日本語/ $ ./dx86cl > Error: value NIL is not of the expected type (OR STRING PATHNAME STREAM). > While executing: PATHNAME-DIRECTORY, in process Initial(0). > Type :GO to continue, :POP to abort, :R for a list of available restarts. > If continued: Skip (possibly crucial) startup function CCL::INIT-LOGICAL-DIRECTORIES. > Type :? for other options. 1 > |
|||
| #481 | fixed | Leopard interface databases | ||
| Description |
We don't provide interface databases that include new Leopard stuff (like NSGradient, for example).
At some fairly near future date, we might want to build interfaces with |
|||
| #600 | fixed | defmethod congruency checks | ||
| Description |
(From Pascal Costanza, http://clozure.com/pipermail/openmcl-devel/2009-September/010353.html) Clozure Common Lisp seems to be too eager in its checking of congruency of generic function lambda lists and those of their methods. Consider the following example: ? (defgeneric foo (a b c))
#<STANDARD-GENERIC-FUNCTION FOO #x30004125B93F>
? (add-method
#'foo
(make-instance 'standard-method
:qualifiers '()
:specializers (list (find-class 't) (find-class 't) (find-class 't))
:lambda-list '(a b c)
:function (lambda (&rest args) (print args))))
> Error: Lambda list of method #<STANDARD-METHOD NIL (T T T)>
> is incompatible with that of the generic function FOO.
> Method's lambda-list : (A B C)
> Generic-function's : (A B C)
While executing: CCL::CHECK-DEFMETHOD-CONGRUENCY, in process
listener(1).
Indeed, check-defmethod-congruency uses the method-function to check for congruency, while it should actually use method-lambda-list for that purpose (at least in non-standard cases). As far as I can tell at the moment, this is the only remaining step so that I can provide compatibility in Closer to MOP of the generic function invocation protocol to the specification in AMOP. |
|||
