Diverse reader errors with Ilisp 5.11, Emacs 21.2.1

I am using Ilisp 5.11, updated with the CVS version as of May 24,2002, CMUCL 18c, Redhat 7.3 and Emacs 21.2.1.

I am getting strange "Reader error"s with this combination. Sometimes it complains of reading a character that is wrong (e.g. #\Space), or a package not found, etc etc. I have not yet been able to track this down much further, but it does seem reminiscent of some bugs reported on this list over the past month or so.

For example, C-z l (load-file-lisp) often chokes. For example, with temp.lisp containing just

(defun foo (a b c d)
  (+ a b c d))

When I try to load-file-lisp I get:


	  * ;;;Compile /home/lyle/temp.lisp

	  Python version 1.0, VM version Intel x86 on 24 MAY 02 04:30:43 pm.
	  Compiling: /home/lyle/temp.lisp 24 MAY 02 04:30:43 pm

	  Converted FOO.
	  Compiling DEFUN FOO: 
	  Byte Compiling Top-Level Form: 

	  /home/lyle/temp.x86f written.
	  Compilation finished in 0:00:00.

	  #p"/home/lyle/temp.x86f"
	  NIL
	  NIL
	  * 
	  Reader error on #<Two-Way Stream, Input = #<Synonym Stream to SYSTEM:*STDIN*>, Output = #<Synonym Stream to SYSTEM:*STDOUT*>>:
	  Package "30" not found.

	  Restarts:
	    0: [ABORT] Return to Top-Level.

	  Debug  (type H for help)

	  (COMMON-LISP::READ-TOKEN
	   #<Two-Way Stream, Input = #<Synonym Stream to SYSTEM:*STDIN*>, Output = #<Synonym Stream to SYSTEM:*STDOUT*>>
	   #\3)
	  Source: Error finding source: 
	  Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM:  Source file no longer exists:
	    target:code/reader.lisp.
	  0] 
		. 
It then appears that the debugger is hung:

	  0] q
	  *


	  Error in KERNEL::UNBOUND-SYMBOL-ERROR-HANDLER:  the variable NO is unbound.

	  Restarts:
	    0: [ABORT] Return to Top-Level.

	  Debug  (type H for help)

	  (EVAL NO)
	  Source: Error finding source: 
	  Error in function DEBUG::GET-FILE-TOP-LEVEL-FORM:  Source file no longer exists:
	    target:code/eval.lisp.
	  0]



Note that the "Reader error" indicates different problems for different source files.

Using instead C-z k (compile-file-lisp) followed by C-z l seems to avoid this problem.

Thanks,

Lyle




_______________________________________________________________

Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm