From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: guile-devel@gnu.org
Subject: Re: Cleanup mark-during-GC debug checks.
Date: Tue, 09 Sep 2008 22:13:02 -0300 [thread overview]
Message-ID: <ga771j$6l1$1@ger.gmane.org> (raw)
In-Reply-To: <87sks9i5ow.fsf@gnu.org>
Ludovic Courtès escreveu:
> Hello!
>
> hanwenn@gmail.com writes:
>
>> Reviewers: hanwenn,
>>
>> Message:
>> Hello guile devel,
>>
>> please go to
>>
>> http://codereview.appspot.com/4847
>>
>> to review this patch.
>>
>>
>> I hope you like it; thanks!
>
> A couple of notes:
>
> 1. I don't want to use a web interface to review code. Most free
> software projects use email in one form or another, which I find
> convenient. Having patches in-lined is optimal IMO.
My experience is that a web interface (which tracks different versions of
the same patch) is a lot easier when it is a major change with lots of
revisions.
In general, I find cutting & pasting patches into emails clumsy and error
prone. In general, git is much better suited for sending patches around.
> 2. I don't want to have a Google account.
>
> Thus, I'll comment on the patch here.
>
> * I'd name the macro `SCM_DEBUG_MARK_PHASE' rather, as it sounds mot
> idiomatic (but I'm not a native speaker).
It's rather the reverse: ensuring that the non-mark phase is correct (in
not having mark calls), but I couldn't think of a good name.
> * Use "static const char msg[] = ...".
done.
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
next prev parent reply other threads:[~2008-09-10 1:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 14:39 Cleanup mark-during-GC debug checks hanwenn
2008-09-09 17:34 ` Ludovic Courtès
2008-09-09 18:15 ` Andy Wingo
2008-09-10 1:13 ` Han-Wen Nienhuys [this message]
2008-09-10 7:36 ` Ludovic Courtès
2008-09-10 19:12 ` 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='ga771j$6l1$1@ger.gmane.org' \
--to=hanwen@xs4all.nl \
--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).