Subject: bug#40671: [DOC] modify literal objects

From: Andreas Schwab <[email-masked]>
Date: Sat, 25 Apr 2020 08:00:37 +0200

On Apr 24 2020, Paul Eggert wrote:

> diff --git a/doc/lispref/objects.texi b/doc/lispref/objects.texi
> index 1eda94ab63..b4e9ff4411 100644
> --- a/doc/lispref/objects.texi
> +++ b/doc/lispref/objects.texi
> @@ -2401,8 +2401,8 @@ Constants and Mutability
>  call @code{(make-string 3 ?a)} yields a mutable string that can be
>  changed via later calls to @code{aset}.
>  
> -  A mutable object can become constant if it is passed to the
> -@code{eval} function, because a program should not modify an object
> +  A mutable object can become constant if it is part of an expression
> +that is evaluated, because a program should not modify an object
>  that is being evaluated.  The reverse does not occur: constant objects

"that is evaluated ... that is being evaluated" is saying the same thing
twice.

Andreas.

-- 
Andreas Schwab, [email-masked]
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."