From: Michael Albinus <michael.albinus@gmx.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: scratch/list-threads 833a2d4 2/9: Make lisp/thread.el the new home for thread-related Lisp functions
Date: Fri, 31 Aug 2018 15:41:17 +0200 [thread overview]
Message-ID: <87tvnaslfm.fsf@gmx.de> (raw)
In-Reply-To: <jwvsh2uektq.fsf-monnier+gmane.emacs.devel@gnu.org> (Stefan Monnier's message of "Fri, 31 Aug 2018 09:19:58 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Actually, fboundp is a much more common way to perform such tests,
> especially since it can silence some warnings at the same occasion.
If we want to discourage the use of featurep, it shall be documented.
I, for example, regard it as natural way to test compatibility.
> (featurep 'xemacs) is an important exception, tho.
This test is not relevant anymore, isn't it?
> What's wrong with (fboundp 'make-thread)?
It returns t already for Emacs 26. If we go this way, (bound-and-true-p
main-thread) would be the better choice, as proposed by Gemini.
> Stefan
Best regards, Michael.
next prev parent reply other threads:[~2018-08-31 13:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180827155307.16925.11045@vcs0.savannah.gnu.org>
[not found] ` <20180827155309.D5C18209C1@vcs0.savannah.gnu.org>
2018-08-29 13:51 ` scratch/list-threads 833a2d4 2/9: Make lisp/thread.el the new home for thread-related Lisp functions Michael Albinus
2018-08-31 0:57 ` Gemini Lasswell
2018-08-31 7:23 ` Michael Albinus
2018-08-31 13:19 ` Stefan Monnier
2018-08-31 13:41 ` Michael Albinus [this message]
2018-08-31 15:16 ` Stefan Monnier
2018-08-31 15:07 ` Eli Zaretskii
2018-09-03 13:14 ` Stefan Monnier
2018-09-03 14:15 ` Michael Albinus
2018-09-03 15:07 ` Eli Zaretskii
2018-09-03 15:17 ` Stefan Monnier
2018-09-05 16:49 ` Gemini Lasswell
2018-09-05 17:48 ` Eli Zaretskii
2018-09-03 10:08 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tvnaslfm.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.