From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Return value of finished threads
Date: Fri, 20 Jul 2018 18:08:15 +0300 [thread overview]
Message-ID: <83zhymymg0.fsf@gnu.org> (raw)
In-Reply-To: <87h8kuq7kf.fsf@gmx.de> (message from Michael Albinus on Fri, 20 Jul 2018 16:56:48 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Fri, 20 Jul 2018 16:56:48 +0200
>
> What I'm missing is a simple possibility to collect the return values of
> the respective finished threads (`find-file-noselect' calls), which is a
> buffer or a list of buffers. The documentation recommends the use of
> global variables, which would be inconvenient for many threads to supervise.
>
> So I'm wondering if we could extend thread support by an indication of
> the thread result, when finished. One idea would be that `thread-join'
> returns with that value.
>
> Another idea, even broader, would be to extend `condition-notify' by an
> argument, which passes a Lisp object to another thread. The
> corresponding `condition-wait' would return that value.
Do you have an implementation in mind? Because in general, passing
variables between threads in C also needs global variables...
next prev parent reply other threads:[~2018-07-20 15:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 14:56 Return value of finished threads Michael Albinus
2018-07-20 15:08 ` Eli Zaretskii [this message]
2018-07-20 15:15 ` Michael Albinus
2018-07-20 16:17 ` Clément Pit-Claudel
2018-07-20 17:25 ` Eli Zaretskii
2018-07-20 16:17 ` Noam Postavsky
2018-07-20 17:31 ` Eli Zaretskii
2018-07-21 9:28 ` Michael Albinus
2018-07-20 18:14 ` Tom Tromey
2018-07-21 9:39 ` Michael Albinus
2018-07-21 13:07 ` Tom Tromey
2018-07-21 13:16 ` Michael Albinus
2018-07-21 14:19 ` Tom Tromey
2018-07-21 14:33 ` Michael Albinus
2018-07-21 18:16 ` Tom Tromey
2018-07-21 19:33 ` Michael Albinus
2018-07-21 21:39 ` Tom Tromey
2018-07-22 10:02 ` Michael Albinus
2018-07-21 22:49 ` Brett Gilio
2018-07-22 2:18 ` Tom Tromey
2018-07-23 18:02 ` Brett Gilio
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=83zhymymg0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.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 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.