From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 29462@debbugs.gnu.org
Subject: bug#29462: 24.4; eval-when-compile won't mute warning as says in info doc
Date: Mon, 27 Nov 2017 18:29:25 +0200 [thread overview]
Message-ID: <83mv3765y2.fsf@gnu.org> (raw)
In-Reply-To: <87h8tgqw2p.fsf@web.de> (message from Michael Heerdegen on Mon, 27 Nov 2017 03:44:46 +0100)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Date: Mon, 27 Nov 2017 03:44:46 +0100
>
> Emanuel Berg <moasen@zoho.com> writes:
>
> > In (info "(elisp) Warning Tips"), it says
> >
> > * If you use many functions and variables
> > from a certain file, you can add
> > a ‘require’ for that package to avoid
> > compilation warnings for them.
> > For instance,
> >
> > (eval-when-compile
> > (require 'foo))
>
> Thanks for the report.
>
> I find this whole sentence confusing and misleading in general. The
> main purpose of `require' is not to silence warnings, and calling it is
> very often something needed, not only something one "can" do.
The above citation is from a section which explains how to avoid
warnings. It is not the place where we document 'require' itself,
only its use to avoid warnings. So reading that out of context as a
statement of the main purpose of 'require' is a mistake, as 'require'
is fully documented elsewhere in the manual.
In the context of avoiding warnings, I see no problem in mentioning
'require'.
next prev parent reply other threads:[~2017-11-27 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 1:21 bug#29462: 24.4; eval-when-compile won't mute warning as says in info doc Emanuel Berg
2017-11-27 2:44 ` Michael Heerdegen
2017-11-27 2:49 ` Emanuel Berg
2017-11-27 16:31 ` Eli Zaretskii
2017-11-27 16:29 ` Eli Zaretskii [this message]
2017-11-27 16:26 ` Eli Zaretskii
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=83mv3765y2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29462@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
/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).