[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: |
Thu, 24 Nov 2022 11:50:56 -0800 |
Matt Armstrong <matt@rfc20.org> writes:
> Note that in my case I had (require 'calc) in the file that used the
> `calc-eval-error' symbol. The info docs for calc state that (require
> 'calc) loads nearly everything you need from calc. I may not understand
> something about the design constraints here, but it seems strange to
> refrain from autoloading this symbol, since (require 'calc) already
> (auto)loads a *lot* of stuff.
So you are saying that if you have a file foo.el, that requires calc,
and then tries to use calc-eval-error variable (documented as part of
the external API), you get a byte-compiler warning?
I agree that this doesn't sound very intuitive.
> My first impression is that adding `defvar' to squash bytecomp warnings
> for symbols in other packages is the wrong default action, and that the
> best idea is for
>
> (require 'foo)
>
> to provide all symbols 'foo-' that one might need when using the `foo'
> package in the normal way.
So I think we could install your patch.