Custom Query (1030 matches)

(loop named nil do (return 1)) does not establish a block at all instead of one named NIL, as I'd expect from 6.1.1.5.6: "The loop named construct gives a name for the block of the loop". There's no mention that specifying the name as NIL instead of defaulting to NIL through omission allows for the omission of the loop block.

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.

This seems to be due to a change in behavior introduced in OS X somewhere between Snow Leopard and Mavericks (I can't tell you exactly where because I skipped the Lions). If you do a text search using cmd-F in a Hemlock window the cursor does not move to the selected text. So if you type something after a cmd-F search, you don't replace the selected text, but instead go back to the position in the file where you were before the search began.