Custom Query (1030 matches)

A #\null character in a lisp file causes the remainder of the file (after the #\Null) to quietly not appear if you open such a file in Hemlock in the Cocoa IDE.

If you then save this file, the file gets truncated after the #\null character.

Leaving aside the issue of how such a character would find its way into a Lisp file in the first place, this is certainly poor behavior on the part of the editor. Other utilities in the IDE (like the Search Files grepper) don't seem to have a problem with #\null characters in files.

Start a fresh CCL 1.6 (64bit Mac OS 10.6.7) and eval the following two forms; this will work as it should.

(defstruct foo a)

(defun baz () (flet ((foo-a (x y) (+ x y))) (foo-a 1 2)))

Now put the two forms in a file, and load the file. The result is a compiler error:

? (load "Users/brooks/Desktop/test.lisp")

Error: While compiling BAZ :

Extra args (1 2) for (LAMBDA (FOO) ...), in process Listener(6).

Alternatively, if the flet defined foo-a to have a single arg, then the compiler would not complain, but subsequently eval'ing (baz) will generate a type error:

? (baz)

Error: value 2 is not of the expected type FOO.

Somewhere in my code is a bug, but it's hard to track down.

? (gen-game)
> Error: value . is not of the expected type LIST.
> While executing: (:INTERNAL (PRINT-OBJECT (CL-ROGUE:LEVEL T))), in process listener(1).

Only by trial and error can I find out which function call is to blame.

Please list the calling functions in an error trace, not just "process listener".