unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Terrific Dead Lock
Date: Tue, 18 Mar 2008 22:20:56 +0100	[thread overview]
Message-ID: <87prtriv9j.fsf@gnu.org> (raw)
In-Reply-To: 87k5k1c4zm.fsf@ossau.uklinux.net

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.

Sure.  (I browsed this thread recently and I think these were mainly
efficiency concerns.)

> - 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.

I dislike the idea of having to create another version of `srcprop' just
for the sake of leaving private macros publicly accessible, but maybe
I'm just too lazy or radical.

FWIW, http://www.google.com/codesearch?hl=en&q=+SRCPROPSP suggests that
Guile may be the only user of this macro.

Thanks,
Ludovic.





  reply	other threads:[~2008-03-18 21:20 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 [this message]
2008-04-14 14:29     ` Ludovic Courtès
2008-04-15 21:06       ` Neil Jerram
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=87prtriv9j.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-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.
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).