From: Andy Wingo <wingo@pobox.com>
To: Ken Raeburn <raeburn@raeburn.org>
Cc: guile-devel Development <guile-devel@gnu.org>
Subject: Re: thread safe functions
Date: Mon, 23 May 2011 22:38:36 +0200 [thread overview]
Message-ID: <m3k4dhp2yb.fsf@unquote.localdomain> (raw)
In-Reply-To: <293BAADA-EF04-4983-A628-1355BDF964ED@raeburn.org> (Ken Raeburn's message of "Tue, 15 Feb 2011 12:18:50 -0500")
On Tue 15 Feb 2011 18:18, Ken Raeburn <raeburn@raeburn.org> writes:
> On Feb 10, 2011, at 17:19, Andy Wingo wrote:
>>> procproc.c: There's a mutex to protect overrides, but it looks like
>>> set-procedure-property! doesn't use it correctly; it should look more
>>> like set-object-property! does.
>>
>> I'm going to punt on this one, since it cannot access the hash table
> in
>> an inconsistent state, and I don't care enough about what happens when
>> multiple threads start changing the same procedure property (a fairly
>> legacy interface) at once. Furthermore there is always (assq-set!
>> (procedure-properties foo) 'bar) to contend with...
>
> It doesn't need to be the same property; I think different threads
> setting different new properties on a procedure in parallel may lose.
Indeed. Fixed.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-05-23 20:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100805112743.GA1671@securactive.net>
[not found] ` <m3vd77vrs0.fsf@unquote.localdomain>
2010-08-22 0:57 ` thread safe functions Ken Raeburn
2010-08-28 19:20 ` Andy Wingo
2010-08-29 1:33 ` Ken Raeburn
2011-02-10 22:19 ` Andy Wingo
2011-02-15 16:00 ` Ken Raeburn
2011-05-23 20:25 ` Andy Wingo
2011-02-15 17:18 ` Ken Raeburn
2011-05-23 20:38 ` Andy Wingo [this message]
2011-05-24 20:57 ` Andy Wingo
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3k4dhp2yb.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=raeburn@raeburn.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.
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).