From bdf32241549a066fc60468129a8705ce3b4232a4 Mon Sep 17 00:00:00 2001 From: Stefan Kangas Date: Tue, 10 Dec 2024 19:23:00 +0100 Subject: [PATCH] Delete obsolete comment about using purespace * src/alloc.c (Fmake_byte_code): Delete obsolete comment. (cherry picked from commit b299a5d184542cdc66632b1a47947151a11c035e) --- src/alloc.c | 7 ------- 1 file changed, 7 deletions(-) diff --git a/src/alloc.c b/src/alloc.c index 9fcf828a918..da6ec52ec3b 100644 --- a/src/alloc.c +++ b/src/alloc.c @@ -3692,13 +3692,6 @@ usage: (make-byte-code ARGLIST BYTE-CODE CONSTANTS DEPTH &optional DOCSTRING INT /* Bytecode must be immovable. */ pin_string (args[CLOSURE_CODE]); - /* We used to purecopy everything here, if purify-flag was set. This worked - OK for Emacs-23, but with Emacs-24's lexical binding code, it can be - dangerous, since make-byte-code is used during execution to build - closures, so any closure built during the preload phase would end up - copied into pure space, including its free variables, which is sometimes - just wasteful and other times plainly wrong (e.g. those free vars may want - to be setcar'd). */ Lisp_Object val = Fvector (nargs, args); XSETPVECTYPE (XVECTOR (val), PVEC_CLOSURE); return val; -- 2.39.5