Common Lisp

When creating a dump from OpenEdge (Progress) database, boolean fields will contain the following values:

• "yes" - true
• "no" - false
• "?" - null. I am assuming that everything else than yes/no is null here.

The example in the section on walking/traversing directories lists the arguments of the uiop:collect-sub*directories

It would be good to reorder the list in the order of this function's arguments like so:

• a directory
• a collectp function
• a recursep function
• a collector function

That will make the example more readable

The documentation for advise ([http://ccl.clozure.com/docs/ccl.html#advising]) is buggy. Instead of arglist both examples should say (car arglist).

Want to back this issue? Post a bounty on it! W

with error:

There is no applicable method for the generic function
  #<STANDARD-GENERIC-FUNCTION CLIM:PANE-NEEDS-REDISPLAY (4)>
when called with arguments
  (NIL).
   [Condition of type SB-PCL::NO-APPLICABLE-METHOD-ERROR]
See also:
  Common Lisp Hyperspec, 7.6.6 [:section]

Restarts:
 0: [RETRY] Retry calling the generic function.
 1: [CLEAR-PANE-TRY-AGAIN] Clear the output his

There seems to be confusion between 'schedule' and 'scheduler' throughout sources and doc. They seem to be used interchangeably, which seems confusing. Is a "schedule" the same as a "scheduleR"?

For example, consider the following code snippet in src/compressor/compressor.lisp:

  (let ((lschedule (make-lscheduler)))
    ;; load up the logical schedule

The variable lschedule and

It looks like the upcoming sbcl 2.0.1 release includes changes to move certain symbols out of cl:*features* and into sb-impl:+internal-features+ [[1]]. IIUC, any "non-public" features will continue to work (for now), but issue a warning [[2]].

I haven't tested it, but it looks like we use at least one such soon-to-be-deprecated feature, namely avx2. We should figure out what to do about