From: Daniel Colascione <dancol@dancol.org>
To: Tom Tromey <tromey@redhat.com>
Cc: Emacs discussions <emacs-devel@gnu.org>
Subject: Re: [PATCH 06/10] add most lisp-level features
Date: Thu, 09 Aug 2012 18:45:35 -0700 [thread overview]
Message-ID: <502467BF.2020301@dancol.org> (raw)
In-Reply-To: <87a9y3etto.fsf@fleche.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
On 8/9/2012 12:41 PM, Tom Tromey wrote:
> This adds most of the thread features visible to emacs lisp.
>
> I roughly followed the Bordeaux threads API:
>
> http://trac.common-lisp.net/bordeaux-threads/wiki/ApiDocumentation
>
> ... but not identically. In particular I chose not to implement
> interrupt-thread or destroy-thread, but instead a thread-signalling
> approach.
Thank you. Functions like that lead to nothing but trouble.
> I'm still undecided about *default-special-bindings* (which I did not
> implement). I think it would be more emacs-like to capture the let
> bindings at make-thread time, but IIRC Stefan didn't like this idea
> the first time around.
I'm with Stefan here. Capturing the bindings at thread-creation time makes the
binding in effect for a thread worker hard to reason about. Say Gnus binds *foo*
and calls into bar-lib, which internally uses threads. bar-lib's thread worker
has no idea *foo* is bound, and if a non-Gnus caller uses bar-lib, *foo* won't
be bound. I feel like this approach would lead to hard-to-find bugs.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]
next prev parent reply other threads:[~2012-08-10 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 19:41 [PATCH 06/10] add most lisp-level features Tom Tromey
2012-08-10 1:45 ` Daniel Colascione [this message]
2012-08-13 14:51 ` Tom Tromey
2012-08-13 20:46 ` Stefan Monnier
2012-08-13 21:02 ` Tom Tromey
2012-08-14 1:13 ` Stefan Monnier
2012-08-14 14:46 ` Tom Tromey
2012-08-14 15:05 ` Stefan Monnier
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=502467BF.2020301@dancol.org \
--to=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=tromey@redhat.com \
/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).