[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
worrying about byte-compiler warnings [was: Flycheck reports are never
worrying about byte-compiler warnings [was: Flycheck reports are never satisfying!?]
Thu, 28 Aug 2014 08:51:05 -0700 (PDT)
>> In such cases, the packages (which use "externals") will output as
>> many warnings as well, for references to "undefined variables"?
> If you take a 20 year old package that hasn't been updated, then the
> byte-compiler will usually emit many such warnings, yes.
Though it does not make the claim that the presence of many warnings
indicates that a package is out of date, someone might well misread
that statement and be misled by it.
So let me be clear: Byte-compiler warnings are not necessarily a sign
that a package has not been updated or it has a coding problem.
A package that works with multiple Emacs versions will often lead to
byte-compiler warnings, possibly many of them, that do not represent
And if the oldest Emacs version supported by a package does not support
things like `declare-function' then there can be even more warnings,
due to function arity changes over time (function-not-known-to-be-defined
In general, my advice to package users would be to not worry about
byte-compiler warnings. They are mainly helpful for package developers
or maintainers (who should be checking them).
If you are a Lisp-savvy user and you want to report a compiler warning
that you think might indicate a problem then, by all means, do let the
package maintainer know. But most of the time users can and typically
should ignore byte-compiler warnings for 3rd-party packages, IMHO,
especially for packages that claim to support multiple Emacs versions.
A notable exception are undefined-variable warnings. It is trivial
for a package maintainer to prevent an inappropriate undefined-variable
warning, no matter how old the Emacs versions supported by the package.
So if a user sees such a warning then yes, that is probably worth
reporting to the package maintainer.
And of course it is always OK to err on the side of caution and feel
free to report anything you see to a package maintainer. My point is
only that users need not _worry_ just because they might see a bunch
of byte-compiler warnings.
Message not available
Re: Flycheck reports are never satisfying!?, Sebastian Wiesner, 2014/08/28