X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=lisp%2Fbytecomp-runtime.el;h=adbc4e1e5cf431c8d6289ce7112f9ed4a97a264e;hb=3b439822d3022408a680b56a171ce04d417f080c;hp=f146c69cef0a08425029b5ba4b207f054fb02e7e;hpb=afa9772e3fcbb4e80e3e4cfd1a40b4fccc6d08b8;p=chise%2Fxemacs-chise.git.1 diff --git a/lisp/bytecomp-runtime.el b/lisp/bytecomp-runtime.el index f146c69..adbc4e1 100644 --- a/lisp/bytecomp-runtime.el +++ b/lisp/bytecomp-runtime.el @@ -92,7 +92,7 @@ They will only be compiled open-coded when `byte-optimize' is true." ; ''byte-optimizer ''byte-compile-inline-expand)))) (defun make-obsolete (fn new) - "Make the byte-compiler warn that FUNCTION is obsolete. + "Make the byte-compiler warn that function FN is obsolete. The warning will say that NEW should be used instead. If NEW is a string, that is the `use instead' message." (interactive "aMake function obsolete: \nxObsoletion replacement: ") @@ -104,7 +104,7 @@ If NEW is a string, that is the `use instead' message." fn) (defun make-obsolete-variable (var new) - "Make the byte-compiler warn that VARIABLE is obsolete, + "Make the byte-compiler warn that variable VAR is obsolete, and NEW should be used instead. If NEW is a string, then that is the `use instead' message." (interactive @@ -119,7 +119,7 @@ and NEW should be used instead. If NEW is a string, then that is the ;; By overwhelming demand, we separate out truly obsolete symbols from ;; those that are present for GNU Emacs compatibility. (defun make-compatible (fn new) - "Make the byte-compiler know that FUNCTION is provided for compatibility. + "Make the byte-compiler know that function FN is provided for compatibility. The warning will say that NEW should be used instead. If NEW is a string, that is the `use instead' message." (interactive "aMake function compatible: \nxCompatible replacement: ") @@ -131,7 +131,7 @@ If NEW is a string, that is the `use instead' message." fn) (defun make-compatible-variable (var new) - "Make the byte-compiler know that VARIABLE is provided for compatibility. + "Make the byte-compiler know that variable VAR is provided for compatibility, and NEW should be used instead. If NEW is a string, then that is the `use instead' message." (interactive