From 88ea6c8120290ff9863678f6bcbeed8fd7869208 Mon Sep 17 00:00:00 2001 From: Paul Eggert Date: Mon, 19 Aug 2024 11:44:44 -0700 Subject: [PATCH] =?utf8?q?Remove=20stray=20obsolete=20comment=20about=20?= =?utf8?q?=E2=80=98volatile=E2=80=99?= MIME-Version: 1.0 Content-Type: text/plain; charset=utf8 Content-Transfer-Encoding: 8bit * src/lisp.h: Remove comment about ‘volatile’ that was mistakenly left behind when 2013-10-03T04:58:56!monnier@iro.umontreal.ca (adf2aa61404305e58e71cde0193bb650aff2c4b3) removed all the volatile members of struct handler. (cherry picked from commit 845d22652d08f998863134334f7de617c50a10b2) --- src/lisp.h | 3 --- 1 file changed, 3 deletions(-) diff --git a/src/lisp.h b/src/lisp.h index c8c6854f5f5..8921244315d 100644 --- a/src/lisp.h +++ b/src/lisp.h @@ -3851,9 +3851,6 @@ record_in_backtrace (Lisp_Object function, Lisp_Object *args, ptrdiff_t nargs) All the other members are concerned with restoring the interpreter state. - Members are volatile if their values need to survive _longjmp when - a 'struct handler' is a local variable. - When running the HANDLER of a 'handler-bind', we need to temporarily "mute" the CONDITION_CASEs and HANDLERs that are "below" the current handler, but without hiding any CATCHERs. We do that by -- 2.39.2