From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: Tom Tromey <tom@tromey.com>, Richard Bunt <richard.bunt@arm.com>,
gdb-patches@sourceware.org, nd@arm.com
Subject: Re: [PATCH v2] Logical short circuiting with argument lists
Date: Sat, 15 Sep 2018 21:03:00 -0000 [thread overview]
Message-ID: <87r2huqxqx.fsf@tromey.com> (raw)
In-Reply-To: <6975e212-9903-2f20-d272-f20d87673504@redhat.com> (Pedro Alves's message of "Wed, 12 Sep 2018 14:04:09 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> On 09/12/2018 12:38 PM, Tom Tromey wrote:
Rich> However, if I had used a space between the array symbol name
Rich> and the parenthesizes this would have been a problem. This is
Rich> useful to know.
>>
>> Yeah. A bit subtle for my taste, I feel certain I'll break this rule by
>> accident.
Pedro> I've extended the wiki section to hopefully clarify things and make it
Pedro> more obvious with an example. Please take a look:
Pedro> https://sourceware.org/gdb/wiki/GDBTestcaseCookbook#Do_not_use_.22tail_parentheses.22_on_test_messages
Thanks for doing that.
Tom
next prev parent reply other threads:[~2018-09-15 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-16 16:03 Richard Bunt
2018-09-04 8:26 ` [PING][PATCH " Richard Bunt
2018-09-07 22:23 ` [PATCH " Tom Tromey
2018-09-07 22:29 ` Simon Marchi
2018-09-07 22:34 ` Simon Marchi
2018-09-07 22:36 ` Tom Tromey
2018-09-08 21:25 ` Simon Marchi
2018-09-12 8:16 ` Richard Bunt
[not found] ` <87pnxjj688.fsf@tromey.com>
2018-09-12 13:04 ` Pedro Alves
2018-09-15 21:03 ` Tom Tromey [this message]
2018-09-17 18:04 ` 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=87r2huqxqx.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.com \
--cc=palves@redhat.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