r7rs-small-texinfo

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs

commit 21e6da9f8c14fd246498ea58a518abf57fc7f54d
parent d0db62e60d9cfeecd992337c6c9f4b83cdaeb6d5
Author: Wolfgang Corcoran-Mathe <wcm@sigwinch.xyz>
Date:   Tue, 30 Jan 2024 15:47:48 -0500

Sec. 3.4: Semantic markup.

Diffstat:
Mdoc/r7rs-small/r7rs-small.texinfo | 10+++++-----
1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/doc/r7rs-small/r7rs-small.texinfo b/doc/r7rs-small/r7rs-small.texinfo @@ -979,11 +979,11 @@ in the appropriate sections of chapter 6. Variables and objects such as pairs, strings, vectors, and bytevectors implicitly denote locationsor sequences of locations. A string, for example, denotes as many locations as there are characters in the string. A new value can be stored into one of these locations -using the string-set! procedure, but the string continues to denote the same locations as +using the @code{string-set!} procedure, but the string continues to denote the same locations as before. -An object fetched from a location, by a variable reference or by a procedure such as car, -vector-ref, or string-ref, is equivalent in the sense of eqv? (section 6.1) to the object last +An object fetched from a location, by a variable reference or by a procedure such as @code{car}, +@code{vector-ref}, or @code{string-ref}, is equivalent in the sense of @code{eqv?} (section 6.1) to the object last stored in the location before the fetch. Every location is marked to show whether it is in use. No variable or object ever refers to a @@ -998,8 +998,8 @@ object. It is also understood that empty strings, empty vectors, and empty bytev which contain no locations, may or may not be newly allocated. Every object that denotes locations is either mutableor immutable. Literal constants, the -strings returned by symbol->string, and possibly the environment returned by -scheme-report-environment are immutable objects. All objects created by the other +strings returned by @code{symbol->string}, and possibly the environment returned by +@code{scheme-report-environment} are immutable objects. All objects created by the other procedures listed in this report are mutable. It is an error to attempt to store a new value into a location that is denoted by an immutable object.