Custom Query (1030 matches)

We found this bug while testing asdf's run-program. This notably matter when invoking CMD.EXE:

? (ccl::make-windows-command-line '("echo" "ok" "1"))
"echo ok 1 " ;; instead of "echo ok 1"

The problem is that due to the time when you shorten the list of string, the test (when strings ...) around printing the space should instead be (when (cdr strings) ...).

PS: you may or may not want to M-x delete-trailing-whitespace and/or have a svn hook that ensures you don't have such whitespace.

We don't compile asdf.lisp during rebuild-ccl, because it had undesirable compile-time side-effects. See r14804, ticket:773, and ticket:765.

ASDF 3's behavior is supposed to be simplified, so it's probably worth taking a look at this again. It may now be harmless to compile asdf.lisp Or, alternately, we could add a stage to rebuild-ccl that compiles an additional set of files (including asdf.lisp) in the newly-build lisp (via run-program). This would prevent compile-time side-effects from messing up the image.

On 32-bit x86:

(defstruct foo (x 0 :type (unsigned-byte 64)))
(make-foo :x 4177526783)

> Error: The value 4177526783 is not of the expected type (UNSIGNED-BYTE 64).