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

Currently the option pane is activated only after pressing it - then it is possible to select the appropriate option in the popup.
This ticket requires writing a handle-event method specialized on the class generic-option-pane and pointer-scroll-event that:

• on scroll up selects the option above (if any, for topmost it is a no-op)
• on scroll down selects the option below (if any, for bo

I am looking for suggestions on ways to make CLOG "feel" lispy - let me know!

sqrt, exponentiation, exp, log, sin, cos, tan, their inverses, etc. aren't implemented. Binding to Lisp isn't the hard part, but coming up with a good standard library design is.

right now, absolute jumps are conflated in the label object here. I'd prefer we instead introduce a new object called absolute-program-location or something like that. (I don't want to use "address" only because it feels too dishonest.) If we do this, then we'd change patch-labels to not overwrite these label objects, and we'

Write a test which does a Rabi experiment and a sine-curve fit on successive RX angles. Something like:

data = []
angles = linspace([0, 2pi], 25)
num_shots = 100
for angle in angles:
    p = RX(angle) 0
    histogram = qvm(p, shots=num_shots)
    data += histogram[1]/num_shots
fit, error = fit_sinusoid(angles, data)
assert error < some_threshold

Intention is to emulate a so