From: msnyder@sonic.net
To: msnyder@sonic.net
Cc: "Bob Rossi" <bob_rossi@cox.net>,
"Nick Roberts" <nickrob@snap.net.nz>,
msnyder@sonic.net, "Daniel Jacobowitz" <drow@false.org>,
gdb-patches@sourceware.org
Subject: ping Re: [PATCH] dead code in mi-interp
Date: Mon, 13 Aug 2007 22:47:00 -0000 [thread overview]
Message-ID: <14206.12.7.175.2.1187045207.squirrel@webmail.sonic.net> (raw)
In-Reply-To: <9770.12.7.175.2.1186782564.squirrel@webmail.sonic.net>
>> On Fri, Aug 10, 2007 at 04:00:18PM +1200, Nick Roberts wrote:
>>> > > It may be that it just wasn't hooked up because the asynchronous
>>> stuff was
>>> > > never completed. Once GDB can work asynchronously then it could
>>> be
>>> > > removed, if not needed. Presumably "no side effects" also means
>>> "can do
>>> > > no harm".
>>> >
>>> > Well, it can always be recovered from the CVS repository if it is
>>> > needed. Personally I'd rathern not have dead code in there just
>>> > because it doesn't do any harm (unles it also has some benefit).
>>>
>>> You would only think of recovering it if you already knew it was there.
>>> I've
>>> just explained what I think is the benefit: they provide possible clues
>>> about
>>> an asynchronous implementation.
>>
>> Even if that was true, the code should be commented out. It really is a
>> bad thing to have code in the program that is meaningless.
>
> And as I recall, the precident is that if you #if 0 something out,
> you remove it.
So it seems like three people favor removing it, and one person opposes.
Can we reach a resolution?
next prev parent reply other threads:[~2007-08-13 22:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 22:25 msnyder
2007-08-08 23:24 ` Nick Roberts
2007-08-09 14:47 ` Jim Blandy
2007-08-09 14:57 ` Daniel Jacobowitz
2007-08-09 21:12 ` Nick Roberts
2007-08-09 21:29 ` msnyder
2007-08-09 22:11 ` Bob Rossi
2007-08-10 4:00 ` Nick Roberts
2007-08-10 11:22 ` Bob Rossi
2007-08-10 21:49 ` msnyder
2007-08-13 22:47 ` msnyder [this message]
2007-08-14 11:27 ` ping " Nick Roberts
2007-08-14 19:51 ` msnyder
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=14206.12.7.175.2.1187045207.squirrel@webmail.sonic.net \
--to=msnyder@sonic.net \
--cc=bob_rossi@cox.net \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
/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