From ca5ade2f0bb132c320e093b33e3b8c5add883016 Mon Sep 17 00:00:00 2001 From: Luc Teirlinck Date: Mon, 2 May 2005 02:47:30 +0000 Subject: [PATCH] (Variable Aliases): `make-obsolete-variable' is a function and not a macro. --- lispref/variables.texi | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/lispref/variables.texi b/lispref/variables.texi index 7320a2eea9f..c8cc8d50f82 100644 --- a/lispref/variables.texi +++ b/lispref/variables.texi @@ -1719,8 +1719,8 @@ variable with a new name. @code{make-obsolete-variable} declares that the old name is obsolete and therefore that it may be removed at some stage in the future. -@defmac make-obsolete-variable variable new &optional when -This macro makes the byte-compiler warn that the variable +@defun make-obsolete-variable variable new &optional when +This function makes the byte-compiler warn that the variable @var{variable} is obsolete. If @var{new} is a symbol, it is the variable's new name; then the warning message says to use @var{new} instead of @var{variable}. If @var{new} is a string, this is the @@ -1729,7 +1729,7 @@ message and there is no replacement variable. If provided, @var{when} should be a string indicating when the variable was first made obsolete---for example, a date or a release number. -@end defmac +@end defun You can make two variables synonyms and declare one obsolete at the same time using the macro @code{define-obsolete-variable-alias}. -- 2.39.2