aboutsummaryrefslogtreecommitdiffstats
path: root/src/alloc.c
diff options
context:
space:
mode:
authorStefan Kangas2024-12-10 19:23:00 +0100
committerStefan Kangas2024-12-12 22:48:20 +0100
commitb299a5d184542cdc66632b1a47947151a11c035e (patch)
tree547e9145562a93793ea148410d70e248344f7d2d /src/alloc.c
parent52dcc032067381f50d658dc43bf7088f1782c7af (diff)
downloademacs-b299a5d184542cdc66632b1a47947151a11c035e.tar.gz
emacs-b299a5d184542cdc66632b1a47947151a11c035e.zip
Delete obsolete comment about using purespace
* src/alloc.c (Fmake_byte_code): Delete obsolete comment.
Diffstat (limited to 'src/alloc.c')
-rw-r--r--src/alloc.c7
1 files changed, 0 insertions, 7 deletions
diff --git a/src/alloc.c b/src/alloc.c
index e1b0259fa8d..5e2747af1f0 100644
--- a/src/alloc.c
+++ b/src/alloc.c
@@ -3764,13 +3764,6 @@ usage: (make-byte-code ARGLIST BYTE-CODE CONSTANTS DEPTH &optional DOCSTRING INT
3764 /* Bytecode must be immovable. */ 3764 /* Bytecode must be immovable. */
3765 pin_string (args[CLOSURE_CODE]); 3765 pin_string (args[CLOSURE_CODE]);
3766 3766
3767 /* We used to purecopy everything here, if purify-flag was set. This worked
3768 OK for Emacs-23, but with Emacs-24's lexical binding code, it can be
3769 dangerous, since make-byte-code is used during execution to build
3770 closures, so any closure built during the preload phase would end up
3771 copied into pure space, including its free variables, which is sometimes
3772 just wasteful and other times plainly wrong (e.g. those free vars may want
3773 to be setcar'd). */
3774 Lisp_Object val = Fvector (nargs, args); 3767 Lisp_Object val = Fvector (nargs, args);
3775 XSETPVECTYPE (XVECTOR (val), PVEC_CLOSURE); 3768 XSETPVECTYPE (XVECTOR (val), PVEC_CLOSURE);
3776 return val; 3769 return val;