[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
scratch/no-purespace f818744cd4b 3/5: Improve purify-flag docstring
From: |
Stefan Kangas |
Subject: |
scratch/no-purespace f818744cd4b 3/5: Improve purify-flag docstring |
Date: |
Sun, 15 Dec 2024 13:37:00 -0500 (EST) |
branch: scratch/no-purespace
commit f818744cd4b1dddece0a221b06e6e83740e06e2d
Author: Stefan Kangas <stefankangas@gmail.com>
Commit: Stefan Kangas <stefankangas@gmail.com>
Improve purify-flag docstring
* src/alloc.c (syms_of_alloc): Improve purify-flag docstring.
---
src/alloc.c | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/src/alloc.c b/src/alloc.c
index 82d1a3a9891..8718121141b 100644
--- a/src/alloc.c
+++ b/src/alloc.c
@@ -7637,13 +7637,11 @@ If this portion is smaller than `gc-cons-threshold',
this is ignored. */);
DEFVAR_LISP ("purify-flag", Vpurify_flag,
doc: /* Non-nil means loading Lisp code in order to dump an
executable.
-This used to mean that certain objects should be allocated in shared (pure)
-space. It can also be set to a hash-table, in which case this table is used
-to do hash-consing of the objects allocated to pure space.
-The hash-consing still applies, but objects are not allocated in pure
-storage any more.
-This flag is still used in a few places not to decide where objects are
-allocated but to know if we're in the preload phase of Emacs's build. */);
+This used to mean that certain objects should be allocated in shared
+(pure) space, but objects are not allocated in pure storage any more.
+This flag is still used in a few places, not to decide where objects are
+allocated, but to know if we're in the preload phase of Emacs's
+build. */);
DEFVAR_BOOL ("garbage-collection-messages", garbage_collection_messages,
doc: /* Non-nil means display messages at start and end of
garbage collection. */);