diff options
Diffstat (limited to 'lisp/emacs-lisp')
| -rw-r--r-- | lisp/emacs-lisp/byte-opt.el | 2 | ||||
| -rw-r--r-- | lisp/emacs-lisp/bytecomp.el | 6 |
2 files changed, 4 insertions, 4 deletions
diff --git a/lisp/emacs-lisp/byte-opt.el b/lisp/emacs-lisp/byte-opt.el index f3cc3d5992e..004f2e28653 100644 --- a/lisp/emacs-lisp/byte-opt.el +++ b/lisp/emacs-lisp/byte-opt.el @@ -1421,7 +1421,7 @@ when (and (listp el) ;; make sure we're at the correct op (eq (nth 1 el) 'byte-constant) (eq (nth 2 el) orig-table)) - ;; jump tables are never resused, so we do this exactly + ;; Jump tables are never reused, so do this exactly ;; once. do (setf (nth 2 el) last-constant) and return nil)))) ;; lap = ( [ (pc . (op . arg)) ]* ) diff --git a/lisp/emacs-lisp/bytecomp.el b/lisp/emacs-lisp/bytecomp.el index e96ba0b6edd..25513bd0248 100644 --- a/lisp/emacs-lisp/bytecomp.el +++ b/lisp/emacs-lisp/bytecomp.el @@ -912,7 +912,7 @@ CONST2 may be evaluated multiple times." (dolist (bytes-tail patchlist) (setq pc (caar bytes-tail)) ; Pick PC from goto's tag. ;; Splits PC's value into 2 bytes. The jump address is - ;; "reconstructued" by the `FETCH2' macro in `bytecode.c'. + ;; "reconstructed" by the `FETCH2' macro in `bytecode.c'. (setcar (cdr bytes-tail) (logand pc 255)) (setcar bytes-tail (lsh pc -8)) ;; FIXME: Replace this by some workaround. @@ -4085,7 +4085,7 @@ Return a list of the form ((TEST . VAR) ((VALUE BODY) ...))" ;; varref var ;; constant #s(hash-table purecopy t data (val1 (TAG1) val2 (TAG2))) ;; switch - ;; goto DEFAUT-TAG + ;; goto DEFAULT-TAG ;; TAG1 ;; <clause body> ;; goto DONETAG @@ -4103,7 +4103,7 @@ Return a list of the form ((TEST . VAR) ((VALUE BODY) ...))" ;; When the opcode argument is `byte-goto', `byte-compile-goto' sets ;; `byte-compile-depth' to `nil'. However, we need `byte-compile-depth' ;; to be non-nil for generating tags for all cases. Since - ;; `byte-compile-depth' will increase by atmost 1 after compiling + ;; `byte-compile-depth' will increase by at most 1 after compiling ;; all of the clause (which is further enforced by cl-assert below) ;; it should be safe to preserve it's value. (let ((byte-compile-depth byte-compile-depth)) |