Re: Mysterious variable name

On Sun, May 12, 2002 at 07:35:47PM +0300, Hannu Koivisto wrote:
> Johan Ur Riise <[email protected]> writes:
> 
> > I use cmucl and ilisp in debian woody. Sometimes this message shows up
> 
> Not all of us use Debian so please specify the version of ILISP
> next time.

apt-cache show ilisp
Version: 5.11.1-5cCLan2

> 
> > Error in KERNEL::UNBOUND-SYMBOL-ERROR-HANDLER:  
> > the variable |^@Q| is unbound.
> >
> > That is caret, commercial at, upper case Q inside multiple escape characters.
> 
> I'd guess ^@ represents a zero byte (you can test it by moving the
> cursor before / on top of ^ and hitting `C-x =' or by moving one
> character right, in which case the cursor should jump before / on
> top of Q (and not before / on top of @ as you might expect if ^ and
> @ were actually separate characters)).
> 
> I have never seen a similar case with a zero byte + Q combination
> but do I see a similar case with one or two zero bytes (IIRC) every
> now and then.  I'm pretty sure this is an ILISP issue and not a
> CMUCL issue (followups set accordingly).

It is a nullbyte, yes. The q I might have typed. This is some of the
input and output:

In the *cmulisp-normal* buffer, I have several GC-outputs, the lisp has
done nothing for a few hours. Then I type a form in a lisp-buffer:
(floor 3 4), and execute it with C-c C-e.
In the *cmulisp-normal* buffer again, first the correct result from the
form, then 0]. I type q (looks like I am in the debugger, but...)

;;;Evaluating floor
0
3
0] 

q


Error in KERNEL::UNBOUND-SYMBOL...

Nothing special with the 0], except there are two spaces after it.


> 
> I may take a look at this at some point (at the moment it's
> slightly over +20°C here so if it is a choice between hacking ILISP
> and taking my Africa Twin for a ride to some nice gravel roads,

lucky you

-- 
Johan Ur Riise
90 15 77 78

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [email protected]