From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Return value of finished threads
Date: Fri, 20 Jul 2018 12:17:04 -0400 [thread overview]
Message-ID: <a9771230-cdf7-b03b-0ac6-403421c5f4af@gmail.com> (raw)
In-Reply-To: <87d0viq6pv.fsf@gmx.de>
On 2018-07-20 11:15, Michael Albinus wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Do you have an implementation in mind? Because in general, passing
>> variables between threads in C also needs global variables...
>
> Not (yet).
>
> I've written this from my use case point of view. It is obvious that
> global variables are needed (maybe kept in a hash or so), but I rather
> give this task to threads.c, instead writing it myself (and urging
> anybody else to write it herself).
On the ELisp side, I wonder if it'd make sense to attach a plist to each thread. With this you would do (thread-put t 'result (returned value)) from the thread, and on the waiting side you'd run thread-join before accessing the result with (thread-get t 'result)
Clément.
next prev parent reply other threads:[~2018-07-20 16:17 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
2018-07-20 15:15 ` Michael Albinus
2018-07-20 16:17 ` Clément Pit-Claudel [this message]
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
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=a9771230-cdf7-b03b-0ac6-403421c5f4af@gmail.com \
--to=cpitclaudel@gmail.com \
--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).