Pascal J. Bourguignon

See https://apple.stackexchange.com/questions/181026/lsopenurlswithrole-failed-with-error-10810-cant-open-install-os-x-yosemite It may be that the newly generated application is quarantined; you can get it out of it with: ``` xattr -l ~/sw/lisp/X86/clozure/ccl-1.12/Foo.app/MacOS/Contents/Foo xattr -dr com.apple.quarantine ~/sw/lisp/X86/clozure/ccl-1.12/Foo.app ```

Now, the problem will recur with the next processor, and the next, etc. Perhaps we should defer to a team with bigger budget, I mean LLVM. A port to LLVM...

The algorithm of `read-delimited-list` is clearly specified in the *description*: ``` read-delimited-list looks ahead at each step for the next non-whitespace[2] character and peeks at it as if with peek-char....

Note that if you want a specific case, you can use format ~:@( or ~( ``` cl-user> (format t "~:@(~X~) ~:*~(~X~)~%" #xbabe) BABE babe nil ```

> with respect to `arithmetic-error-operands`, the suggestion to make them generic functions would probably involve the issue to make condition types into classes, which i put in a branch since...

There are two things here: 1- In normal use. Then I think we should display at INFO level important state transitions. This can inform the user whether it keeps working...

This code works for me on "Version 1.12.1 (v1.12.1-7-g4912320e) Darwinx8664". Try to load, or compile and load the source again. Perhaps you have an old version of foo?

Also, it depends on the optimization. I can reproduce it with the last setting: ``` (declaim (optimize (speed 0) (space 0) (safety 3) (debug 3) (compilation-speed 3))) ; no (declaim...

The problem is that you're asking to print this vector readably. sbcl uses an implementation specific syntax, so it's de-facto non-conforming code. Now there may be a question of interpretation...

Oops, you're right. (I don't like it when the standard allows implementation dependent behavior!)