From: Tom Tromey <tom@tromey.com>
To: Richard Bunt <richard.bunt@arm.com>
Cc: gdb-patches@sourceware.org, nd@arm.com
Subject: Re: [PATCH v3] Logical short circuiting with argument lists
Date: Fri, 14 Sep 2018 21:00:00 -0000 [thread overview]
Message-ID: <87lg833ibu.fsf@tromey.com> (raw)
In-Reply-To: <833f15b2-48da-fe83-86c8-3c2bce46b01c@arm.com> (Richard Bunt's message of "Fri, 14 Sep 2018 09:08:58 +0100")
>>>>> "Richard" == Richard Bunt <richard.bunt@arm.com> writes:
Richard> Version 3 addresses review comments:
Richard> * Removed forward declaration of skip_undetermined_arglist.
Richard> * Made definition of skip_undetermined_arglist static.
Richard> * Added introductory comment to skip_undetermined_arglist.
Richard> * Dropped (*pos)+=3 into the block.
Richard> * Adjusted Tcl bracing.
Richard> * Removed string splitting in the test case.
Thanks again for the patch.
Richard> + if (noside != EVAL_SKIP)
Richard> + {
Richard> + return evaluate_var_value (noside, exp->elts[pc + 1].block, var);
Richard> + }
The gdb style is no braces if there's just a single line.
Richard> + else
Richard> + {
Richard> + /* Return a dummy value of the correct type when skipping, so
Richard> + that parent functions know what is to be skipped. */
Richard> + return allocate_value (SYMBOL_TYPE (var));
... compared to here, where braces are mandatory.
This patch is ok with that first set of braces removed.
(You don't have to re-send it.)
thanks,
Tom
next prev parent reply other threads:[~2018-09-14 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 8:10 Richard Bunt
2018-09-14 21:00 ` Tom Tromey [this message]
2018-09-18 18:39 ` Richard Bunt
2018-10-07 5:14 ` New FAILs on gdb.fortran/short-circuit-argument-list.exp when testing on native{,-extended}-gdbserver (was: Re: [PATCH v3] Logical short circuiting with argument lists) Sergio Durigan Junior
2018-12-03 13:22 ` New FAILs on gdb.fortran/short-circuit-argument-list.exp when testing on native{,-extended}-gdbserver Richard Bunt
2018-12-03 14:58 ` Richard Bunt
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=87lg833ibu.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=richard.bunt@arm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).