[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/lispref/eval.texi
From: |
Richard M. Stallman |
Subject: |
[Emacs-diffs] Changes to emacs/lispref/eval.texi |
Date: |
Fri, 26 Sep 2003 05:59:01 -0400 |
Index: emacs/lispref/eval.texi
diff -c emacs/lispref/eval.texi:1.11 emacs/lispref/eval.texi:1.12
*** emacs/lispref/eval.texi:1.11 Mon Sep 1 11:45:41 2003
--- emacs/lispref/eval.texi Fri Sep 26 05:59:01 2003
***************
*** 588,598 ****
specify limits to the evaluation process, or record recently returned
values. Loading a file also does evaluation (@pxref{Loading}).
! @strong{Note:} it is generally cleaner and more flexible to store a
! function in a data structure, and call it with @code{funcall} or
! @code{apply}, than to store an expression in the data structure and
! evaluate it. Using functions provides the ability to pass information
! to them as arguments.
@defun eval form
This is the basic function evaluating an expression. It evaluates
--- 588,598 ----
specify limits to the evaluation process, or record recently returned
values. Loading a file also does evaluation (@pxref{Loading}).
! It is generally cleaner and more flexible to store a function in a
! data structure, and call it with @code{funcall} or @code{apply}, than
! to store an expression in the data structure and evaluate it. Using
! functions provides the ability to pass information to them as
! arguments.
@defun eval form
This is the basic function evaluating an expression. It evaluates