From: Richard M. Stallman <rms@gnu.org>
Date: Sat, 6 Aug 1994 19:25:24 +0000 (+0000)
Subject: (byte-after-unbind-ops): Fix paren error wrt doc string.
X-Git-Tag: emacs-19.34~7387
X-Git-Url: http://git.eshelyaron.com/gitweb/?a=commitdiff_plain;h=cb88b56ea9ea0a8c2e6ee5a2d61094d432ab93af;p=emacs.git

(byte-after-unbind-ops): Fix paren error wrt doc string.
---

diff --git a/lisp/emacs-lisp/byte-opt.el b/lisp/emacs-lisp/byte-opt.el
index 8b7937b7d80..7bfa75dbaaf 100644
--- a/lisp/emacs-lisp/byte-opt.el
+++ b/lisp/emacs-lisp/byte-opt.el
@@ -1177,10 +1177,10 @@
      byte-symbolp byte-consp byte-stringp byte-listp byte-numberp byte-integerp
      byte-eq byte-equal byte-not
      byte-cons byte-list1 byte-list2	; byte-list3 byte-list4
-     byte-interactive-p
-     ;; How about other side-effect-free-ops?  Is it safe to move an
-     ;; error invocation (such as from nth) out of an unwind-protect?
-     "Byte-codes that can be moved past an unbind."))
+     byte-interactive-p)
+   ;; How about other side-effect-free-ops?  Is it safe to move an
+   ;; error invocation (such as from nth) out of an unwind-protect?
+   "Byte-codes that can be moved past an unbind.")
 
 (defconst byte-compile-side-effect-and-error-free-ops
   '(byte-constant byte-dup byte-symbolp byte-consp byte-stringp byte-listp