unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Philipp Stephani <p.stephani2@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 42425@debbugs.gnu.org, "João Távora" <joaotavora@gmail.com>
Subject: bug#42425: 26.3.50; Compilation warnings when compiling eldoc.el under Emacs 26.3
Date: Sun, 24 Jan 2021 10:30:37 +0100	[thread overview]
Message-ID: <CAArVCkQRZO4KkE1obKAq+1HkY=Wo2H46zhv1xyMqx9VM2y23CA@mail.gmail.com> (raw)
In-Reply-To: <87k0s3v728.fsf@gnus.org>

Am Sa., 23. Jan. 2021 um 19:31 Uhr schrieb Lars Ingebrigtsen <larsi@gnus.org>:
>
> Philipp Stephani <p.stephani2@gmail.com> writes:
>
> >> Doing so seems easy enough, but I'm not sure how high our ambitions are
> >> for doing warning-free ELPA packages on older Emacs versions?  (I've
> >> added João to the CCs.)
> >
> > I think our ambitions should be quite high. (I personally think we
> > should treat almost all compiler warnings as errors/bugs and fix them
> > whenever realistically possible.)
>
> Building Emacs has traditionally been watching a wall of warnings scroll
> by.  This has recently changed, but shows that "no warnings" isn't a
> value held universally by the Emacs developers.
>
> I think that the Emacs build should be warning free -- on our main,
> current targets.  Jumping through hoops to avoid warnings on older Emacs
> versions normally isn't worth spending time on, in my opinion.

Yeah, but here we're talking about moving a single function definition
(eldoc--eval-expression-setup) around, which shouldn't realistically
cause problems.

>
> >> > 2. Probably eldoc should protect against newer Elisp functions being not
> >> >    yet available, as calling such functions will likely result in errors
> >> >    at runtime.
> >>
> >> Doesn't it do that?  What functions is it using that's not available?
> >
> > At least the current master version looks fine, though the byte
> > compiler isn't smart enough to detect that. The problematic uses are
> > in eldoc--eval-expression-setup.
>
> I'm not sure I follow you here -- are you saying that eldoc doesn't work
> on Emacs 26 because of the usages in `eldoc--eval-expression-setup'?

No, the code is correct as far as I can see. The functions that would
be unavailable in Emacs 26 won't be used in Emacs 26. But the byte
compiler detects only checks in the form of (when (fboundp 'FUNC)
(FUNC ...)) and similar, but not the check performed in that function.





  reply	other threads:[~2021-01-24  9:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-19  8:12 bug#42425: 26.3.50; Compilation warnings when compiling eldoc.el under Emacs 26.3 Philipp Stephani
2021-01-22 19:58 ` Lars Ingebrigtsen
2021-01-22 20:22   ` João Távora
2021-01-23 17:35   ` Philipp Stephani
2021-01-23 17:53     ` João Távora
2021-01-23 18:31     ` Lars Ingebrigtsen
2021-01-24  9:30       ` Philipp Stephani [this message]
2021-01-26  0:07         ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAArVCkQRZO4KkE1obKAq+1HkY=Wo2H46zhv1xyMqx9VM2y23CA@mail.gmail.com' \
    --to=p.stephani2@gmail.com \
    --cc=42425@debbugs.gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).