all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Fri, 31 Aug 2018 09:19:58 -0400	[thread overview]
Message-ID: <jwvsh2uektq.fsf-monnier+gmane.emacs.devel@gnu.org> (raw)
In-Reply-To: 877ek780f4.fsf@gmx.de

> It would work, of course. But I'm a finicky German :-) `featurep' is the
> default way in Emacs to check, whether a feature exist, so I've done it
> this way.

Actually, fboundp is a much more common way to perform such tests,
especially since it can silence some warnings at the same occasion.
(featurep 'xemacs) is an important exception, tho.

> So we might provide the feature `threads-supported' or similar in
> src/thread.c. WDYT?

What's wrong with (fboundp 'make-thread)?


        Stefan




  reply	other threads:[~2018-08-31 13:19 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 [this message]
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
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=jwvsh2uektq.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 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.