From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Snyder <msnyder@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: [rfa] more all-target -Werror patches
Date: Tue, 01 Oct 2002 13:15:00 -0000 [thread overview]
Message-ID: <ro1k7l1ud9z.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <ro1ofaet05t.fsf@jackfruit.Stanford.EDU>
On 01 Oct 2002 12:43:42 -0700, David Carlton <carlton@math.Stanford.EDU> said:
> How about I change the existing comment
> /* need to do something here */
> to
> /* FIXME: We need to do something here. For now, just put in a
> semicolon so the label has an expression to stick to. (GCC will
> complain otherwise.) */
> And yes, I realize that FIXME's should ideally have a name attached to
> them, but that name should be the author of the original comment
> rather than mine, and I don't know who that is.
Now that I look at the code, I'm really not sure what comment should
go there. It's not clear to me what the intent of the original
comment is: I'd assumed that it meant that there should be code after
the retry label, but it's not at all clear to me why one would expect
that to be the case: the function looks sensible enough as it is.
So maybe I should leave the initial comment intact, and add the
following comment:
/* NOTE: carlton/2002-10-01: The semicolon is there so the label has
an expression to stick to. (GCC will complain otherwise.) */
David Carlton
carlton@math.stanford.edu
prev parent reply other threads:[~2002-10-01 20:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 9:18 David Carlton
2002-10-01 9:30 ` Andrew Cagney
2002-10-01 12:29 ` David Carlton
2002-10-01 12:32 ` Michael Snyder
2002-10-01 12:37 ` Daniel Jacobowitz
2002-10-01 12:43 ` David Carlton
2002-10-01 13:15 ` David Carlton [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ro1k7l1ud9z.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox