Mercurial > emacs
changeset 104291:a43e99d78f43
* advice.texi (Argument Access in Advice): Note that argument
positions are zero-based (Bug#3932).
| author | Chong Yidong <cyd@stupidchicken.com> |
|---|---|
| date | Sat, 15 Aug 2009 22:02:59 +0000 |
| parents | ced4690576f6 |
| children | 3a381ae2eb0e |
| files | doc/lispref/ChangeLog doc/lispref/advice.texi |
| diffstat | 2 files changed, 8 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/doc/lispref/ChangeLog Sat Aug 15 21:51:33 2009 +0000 +++ b/doc/lispref/ChangeLog Sat Aug 15 22:02:59 2009 +0000 @@ -1,5 +1,8 @@ 2009-08-15 Chong Yidong <cyd@stupidchicken.com> + * advice.texi (Argument Access in Advice): Note that argument + positions are zero-based (Bug#3932). + * commands.texi (Distinguish Interactive): Minor copyedit. * display.texi (Face Attributes): Add xref to Displaying Faces for
--- a/doc/lispref/advice.texi Sat Aug 15 21:51:33 2009 +0000 +++ b/doc/lispref/advice.texi Sat Aug 15 22:02:59 2009 +0000 @@ -603,11 +603,11 @@ A more robust method is to use macros that are translated into the proper access forms at activation time, i.e., when constructing the -advised definition. Access macros access actual arguments by position -regardless of how these actual arguments get distributed onto the -argument variables of a function. This is robust because in Emacs Lisp -the meaning of an argument is strictly determined by its position in the -argument list. +advised definition. Access macros access actual arguments by their +(zero-based) position, regardless of how these actual arguments get +distributed onto the argument variables of a function. This is robust +because in Emacs Lisp the meaning of an argument is strictly +determined by its position in the argument list. @defmac ad-get-arg position This returns the actual argument that was supplied at @var{position}.