mirror of
git://git.sv.gnu.org/emacs.git
synced 2026-02-04 06:31:13 -08:00
* lisp/emacs-lisp/macroexp.el (macroexpand-all-1): Don't handle `lambda'
specially, since it's a macro. Fix up wrong hint passed to maybe-cons.
This commit is contained in:
parent
2a64315a11
commit
49b2e83db4
3 changed files with 5 additions and 7 deletions
|
|
@ -1,5 +1,8 @@
|
|||
2010-06-16 Stefan Monnier <monnier@iro.umontreal.ca>
|
||||
|
||||
* emacs-lisp/macroexp.el (macroexpand-all-1): Don't handle `lambda'
|
||||
specially, since it's a macro. Fix up wrong hint passed to maybe-cons.
|
||||
|
||||
* font-lock.el (font-lock-major-mode): Rename from
|
||||
font-lock-mode-major-mode to distinguish it from
|
||||
global-font-lock-mode's own font-lock-mode-major-mode (bug#6135).
|
||||
|
|
|
|||
|
|
@ -282,7 +282,7 @@ Not documented
|
|||
;;;;;; flet progv psetq do-all-symbols do-symbols dotimes dolist
|
||||
;;;;;; do* do loop return-from return block etypecase typecase ecase
|
||||
;;;;;; case load-time-value eval-when destructuring-bind function*
|
||||
;;;;;; defmacro* defun* gentemp gensym) "cl-macs" "cl-macs.el" "fbeedbf769c72fee9b4e0671957c1077")
|
||||
;;;;;; defmacro* defun* gentemp gensym) "cl-macs" "cl-macs.el" "36cafd5054969b5bb0b1ce6a21605fed")
|
||||
;;; Generated autoloads from cl-macs.el
|
||||
|
||||
(autoload 'gensym "cl-macs" "\
|
||||
|
|
|
|||
|
|
@ -134,7 +134,7 @@ Assumes the caller has bound `macroexpand-all-environment'."
|
|||
(maybe-cons fun
|
||||
(maybe-cons (macroexpand-all-forms (cadr form) 2)
|
||||
nil
|
||||
(cadr form))
|
||||
(cdr form))
|
||||
form)
|
||||
form))
|
||||
((memq fun '(let let*))
|
||||
|
|
@ -145,11 +145,6 @@ Assumes the caller has bound `macroexpand-all-environment'."
|
|||
form))
|
||||
((eq fun 'quote)
|
||||
form)
|
||||
((and (consp fun) (eq (car fun) 'lambda))
|
||||
;; embedded lambda
|
||||
(maybe-cons (macroexpand-all-forms fun 2)
|
||||
(macroexpand-all-forms (cdr form))
|
||||
form))
|
||||
;; The following few cases are for normal function calls that
|
||||
;; are known to funcall one of their arguments. The byte
|
||||
;; compiler has traditionally handled these functions specially
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue