Custom Query (1030 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (253 - 255 of 1030)

Ticket Resolution Summary Owner Reporter
#315 fixed #'<macro op> in a :method clause causes spurious signature incongruity gz james anderson
Description

QRES-GDS> (lisp-implementation-version) "Version 1.2-r9777-working-0711 (LinuxX8664)" QRES-GDS> (defgeneric test-or (a)

(:method ((a sequence))

(reduce #'plus a :key #'identity)))

#<STANDARD-GENERIC-FUNCTION TEST-OR #x30006EF2F15F> QRES-GDS> (defgeneric test-or (a)

(:method ((a sequence))

(reduce #'or a :key #'identity)))

;Compiler warnings : ; In (TEST-OR (SEQUENCE)) inside an anonymous lambda form: FUNCTION can't be used to reference lexically visible macro OR. ; Evaluation aborted.

;;; the slime backtrace buffer contained:

Lambda list of method #<STANDARD-METHOD TEST-OR (SEQUENCE)> is incompatible with that of the generic function TEST-OR. Method's lambda-list : (A) Generic-function's : (A)

[Condition of type SIMPLE-ERROR]

Restarts:

0: [CONTINUE] Remove 0 methods from the generic-function and change its lambda list. 1: [ABORT] Return to SLIME's top level.

Backtrace:

0: (CCL::CHECK-DEFMETHOD-CONGRUENCY #<STANDARD-GENERIC-FUNCTION TEST-OR #x30006EF2F15F> #<STANDARD-METHOD TEST-OR (SEQUENCE)>) 1: (CCL::%ADD-STANDARD-METHOD-TO-STANDARD-GF #<STANDARD-GENERIC-FUNCTION TEST-OR #x30006EF2F15F> #<STANDARD-METHOD TEST-OR (SEQUENCE)>) 2: (CCL::ENSURE-METHOD TEST-OR (#<BUILT-IN-CLASS SEQUENCE>) :FUNCTION #<CCL:METHOD-FUNCTION TEST-OR (SEQUENCE)> :QUALIFIERS NIL :LAMBDA-LIST (A)) 3: (#<Anonymous Function #x30006F896E3F>) 4: (SWANK::EVAL-REGION "(defgeneric test-or (a)

(:method ((a sequence))

(reduce #'or a :key #'identity)))

")

5: ((:INTERNAL SWANK::REPL-EVAL))

...

#316 fixed document JOIN-PROCESS Gary Byers R. Matthew Emerson
Description

Add documentation for JOIN-PROCESS (see ccl:level-1;l1-processes.lisp)

#317 fixed Should provide a way to update the ccl hierarchy Gary Byers gz
Description

Need a function (or an argument to rebuild-ccl) that does the two step process necessary to properly update a ccl hierarchy from subversion: 'svn up' and then 'svn revert' the kernel and image.

The reason for this is that 'svn up' doesn't overwrite modified binaries, so if a user ever did a rebuild-ccl (which they must if they use the trunk), 'svn up' no longer gets the latest checked in binaries. See for example the thread starting with http://clozure.com/pipermail/openmcl-devel/2008-July/008399.html

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.