Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [RFA] breakpoint.c, create_breakpoint, document that the case statement falls through.
Date: Thu, 03 Mar 2011 17:11:00 -0000	[thread overview]
Message-ID: <4D6FCBB1.9040507@vmware.com> (raw)
In-Reply-To: <20110303042652.GU30306@adacore.com>

Joel Brobecker wrote:
>> 2011-03-02  Michael Snyder  <msnyder@vmware.com>
>>
>> 	* breakpoint.c (create_breakpoint): Document that case falls through.
>>
>> Index: breakpoint.c
>> ===================================================================
>> RCS file: /cvs/src/src/gdb/breakpoint.c,v
>> retrieving revision 1.546
>> diff -u -p -u -p -r1.546 breakpoint.c
>> --- breakpoint.c	1 Mar 2011 02:16:56 -0000	1.546
>> +++ breakpoint.c	3 Mar 2011 00:38:01 -0000
>> @@ -7843,6 +7843,7 @@ create_breakpoint (struct gdbarch *gdbar
>>  	default:
>>  	  throw_exception (e);
>>  	}
>> +      /* FALLTHROUGH */
>>      default:
>>        if (!sals.nelts)
>>  	return 0;
> 
> Just some thoughts:
> 
> It's actually never going to fall through, is it? Can we use "break;"
> instead, even if we know it's never going to be reached? I think
> it would make it clearer by not suggesting something that isn't
> supposed to happen (the fall through).
> 

No, honest, it *does* fall through!
I had to use a printf statement to convince myself.   ;-)

When the user answers "yes" to the query, it falls through.


  parent reply	other threads:[~2011-03-03 17:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-03  0:42 Michael Snyder
2011-03-03  4:27 ` Joel Brobecker
2011-03-03  9:55   ` Pedro Alves
2011-03-03 17:11   ` Michael Snyder [this message]
2011-03-03 17:45     ` Tom Tromey
2011-03-04 18:58       ` Michael Snyder

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=4D6FCBB1.9040507@vmware.com \
    --to=msnyder@vmware.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.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