From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA] C++-ify skip.c
Date: Wed, 09 Aug 2017 18:32:00 -0000 [thread overview]
Message-ID: <87valwh9tf.fsf@tromey.com> (raw)
In-Reply-To: <04c97e6e95cf8f012979b6b1052871a0@polymtl.ca> (Simon Marchi's message of "Wed, 09 Aug 2017 11:14:41 +0200")
>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
Simon> That would avoid complicating the calling functions as well.
Simon> Either way (adding std::moves or this) are fine for me, it's as
Simon> you wish.
I've added the moves, and I'm checking it in. Thanks.
Tom
next prev parent reply other threads:[~2017-08-09 18:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 19:42 Tom Tromey
2017-08-07 11:46 ` Simon Marchi
2017-08-07 13:58 ` Tom Tromey
2017-08-07 14:32 ` Simon Marchi
2017-08-08 19:52 ` Tom Tromey
2017-08-09 9:15 ` Simon Marchi
2017-08-09 18:32 ` Tom Tromey [this message]
2017-08-10 19:34 ` [PATCH] More gdb/skip.c C++ification Pedro Alves
2017-08-10 19:51 ` Pedro Alves
2017-08-10 21:10 ` Tom Tromey
2017-08-11 11:23 ` Pedro Alves
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=87valwh9tf.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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