From: Stefan Monnier <monnier@iro.umontreal.ca>
To: 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: Mon, 03 Sep 2018 11:17:54 -0400 [thread overview]
Message-ID: <jwvk1o2txuw.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 83ftyqzkj6.fsf@gnu.org
>> >> What's wrong with (fboundp 'make-thread)?
>> > That (AFAIK) it returns non-nil even when threads are not available?
>> What is the reason for this?
> AFAIR, that was how Tom wrote the code in the first place. It makes
> the configury slightly less complicated, and makes extending the
> low-level support to other threading libraries slightly easier. Not
> very important reasons, but then we do have other features that just
> do nothing useful on platforms where they cannot be supported.
Hmm... I see. That's too bad: (fboundp 'make-thread) seems like the
most natural way to check for availability of threading.
> No. AFAIK, all platforms that support threads either don't need any
> library, or load it right at the beginning.
That was my impression,
Stefan
next prev parent reply other threads:[~2018-09-03 15:17 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
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 [this message]
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
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=jwvk1o2txuw.fsf-monnier+gmane.emacs.devel@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@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).