Re: lread.c's `values' variable

[Kim F. Storm]

Richard Stallman <address@hidden> writes:

>     Yes, it uses (car values).
> 
> values is supposed to provide a history that you can look at whenever
> you wish.

Has anyone ever needed to look at that list?

Isn't the information typically found in the *Messages* buffer, in the
command history, or in the buffer where you evalled the expression
(e.g. *scratch*).

>  It's not just meant for the functions that look at it.

It is quite obvious that functions can only really look at the car of
that list.  So it is really _never_ for functions to look at (as a list).

> 
>     However, that doesn't explain why `values' needs to be a list of all
>     expressions "which were read, evaluated and printed".  Since it grows
>     without ever being truncated, it is a memory leak IMO.
> 
> It probably is not a significant leak, but if it is, we could make GC
> truncate it to a certain length.

If we keep it as a list, I think that is a reasonable compromise.

-- 
Kim F. Storm <address@hidden> http://www.cua.dk