From: Neil Jerram <neil@ossau.uklinux.net>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Terrific Dead Lock
Date: Tue, 15 Apr 2008 22:06:43 +0100 [thread overview]
Message-ID: <87ve2i4yl8.fsf@ossau.uklinux.net> (raw)
In-Reply-To: <87fxtoik6a.fsf@gnu.org> (Ludovic Courtès's message of "Mon, 14 Apr 2008 16:29:49 +0200")
ludo@gnu.org (Ludovic Courtès) writes:
> Hi,
>
> Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> Basically yes, but two thoughts:
>>
>> - Can I just take a couple more days to review the srcprops changes in
>> detail? It's important for my debugging work, and I recall having
>> some concern when Han-Wen implemented this... Looking at the diffs
>> quickly again now, I can't see any reason for that concern, but I'd
>> like to be sure.
>>
>> - Although I agree in principle that all those macros shouldn't be in
>> srcprop.h, do we really need to make that change now? I think we can
>> just apply Han-Wen's changes to the macros in srcprop.h, without
>> moving them to srcprop.c.
>
> Are you OK to apply the patch?
Yes, fine. Sorry for forgetting about this.
(I wonder if SCM_CDR (scm_last_plist_filename) on one thread is
guaranteed to give a sane value, if there is another thread
simultaneously doing SCM_SETCDR (scm_last_plist_filename) - but I'm
not an expert in this kind of thing.)
Regards,
Neil
next prev parent reply other threads:[~2008-04-15 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 22:29 Terrific Dead Lock Ludovic Courtès
2008-03-14 10:24 ` Ludovic Courtès
2008-03-17 23:20 ` Neil Jerram
2008-03-18 21:20 ` Ludovic Courtès
2008-04-14 14:29 ` Ludovic Courtès
2008-04-15 21:06 ` Neil Jerram [this message]
2008-04-16 10:03 ` Ludovic Courtès
2008-04-16 20:29 ` Neil Jerram
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=87ve2i4yl8.fsf@ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=ludo@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.
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).