[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#58801: [PATCH] Autoload the `calc-eval-error' variable
From: |
Stefan Kangas |
Subject: |
bug#58801: [PATCH] Autoload the `calc-eval-error' variable |
Date: |
Fri, 11 Nov 2022 05:16:42 -0800 |
Matt Armstrong <matt@rfc20.org> writes:
> From 526d0b31e0d836e7a3c21d831849b8c50da2420e Mon Sep 17 00:00:00 2001
> From: Matt Armstrong <matt@rfc20.org>
> Date: Wed, 26 Oct 2022 09:46:37 -0700
> Subject: [PATCH] Autoload the `calc-eval-error' variable
>
> * lisp/calc/calc-aent.el: Autoload the `calc-eval-error' variable,
> because it is documented as a lisp level option of the `calc-eval'
> function, which is also autoloaded. Otherwise, even (require 'calc)
> is not enough to get the variable defined; `calc-eval' must actually
> be evaluated. This squashes byte compiler warnings in code using the
> variable.
I don't necessarily object strongly or anything, but should we really
autoload a variable just to squash byte compiler warnings?
I think the usual way to do that is to say
(defvar calc-eval-error)
in the calling code.
> ---
> lisp/calc/calc-aent.el | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lisp/calc/calc-aent.el b/lisp/calc/calc-aent.el
> index ef3e0d4b67..59692beff7 100644
> --- a/lisp/calc/calc-aent.el
> +++ b/lisp/calc/calc-aent.el
> @@ -252,6 +252,7 @@ calc-do-calc-eval
> res (cdr res)))
> buf)))))))))
>
> +;;;###autoload
> (defvar calc-eval-error nil
> "Determines how calc handles errors.
> If nil, return a list containing the character position of error.
- bug#58801: [PATCH] Autoload the `calc-eval-error' variable,
Stefan Kangas <=