From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35433@debbugs.gnu.org
Subject: bug#35433: 27.0.50; 'function' docstring: tell more about advantages?
Date: Thu, 23 May 2019 18:55:08 +0200 [thread overview]
Message-ID: <87r28p1577.fsf@web.de> (raw)
In-Reply-To: <83blzt7pcb.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 23 May 2019 07:43:32 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> > From: Michael Heerdegen <michael_heerdegen@web.de>
> > Cc: 35433@debbugs.gnu.org
> > Date: Thu, 23 May 2019 01:39:49 +0200
> >
> > +When @var{function-object} is a symbol and the code is byte compiled,
> > +the byte-compiler will warn should that function be undefined or may
> > +be unknown at run-time.
>
> I'd say "... will warn if that function is not defined, which means
> it might not be known at run time" instead.
No, these are two different cases: (1) function not known when
compiling, and (2) known to the compiler but function may still be
unknown when the compiled code is run, because the compiled file misses
`require' statements, for example.
> "Undefined" and "unknown" sound vague and more ominous to me.
Well, I tried to reuse the words from the actual compiler warnings - see
`byte-compile-warn-about-unresolved-functions'. I may change "may be
unknown" to "may not be known" - unless you have a better idea:
+When @var{function-object} is a symbol and the code is byte compiled,
+the byte-compiler will warn should that function be undefined or may
+not be known at run-time.
Thanks,
Michael.
next prev parent reply other threads:[~2019-05-23 16:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-26 3:40 bug#35433: 27.0.50; 'function' docstring: tell more about advantages? Michael Heerdegen
2019-04-26 6:48 ` Eli Zaretskii
2019-04-27 8:30 ` Michael Heerdegen
2019-04-27 8:47 ` Eli Zaretskii
2019-05-22 23:39 ` Michael Heerdegen
2019-05-23 4:43 ` Eli Zaretskii
2019-05-23 16:55 ` Michael Heerdegen [this message]
2019-05-23 18:31 ` Eli Zaretskii
2019-05-23 23:18 ` Michael Heerdegen
2019-05-24 6:42 ` 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=87r28p1577.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=35433@debbugs.gnu.org \
--cc=eliz@gnu.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).