From: Simon Marchi <simon.marchi@polymtl.ca>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Make encode_actions_rsp use std::vector
Date: Thu, 09 Nov 2017 00:49:00 -0000 [thread overview]
Message-ID: <55f80ffd6b010b3bc1648112c188f2be@polymtl.ca> (raw)
In-Reply-To: <e3540e638ddd2b99579ad92d9373461e@polymtl.ca>
On 2017-10-29 22:33, Simon Marchi wrote:
> On 2017-10-29 22:29, Simon Marchi wrote:
>> Currently, encode_actions_rsp returns two malloc'ed arrays of
>> malloc'ed
>> strings (char *) by pointer. Change this to use
>> std::vector<std::string>. This eliminates some cleanups in remote.c.
...
> Woops, I left the local vector name "str_list2", a temporary name I
> gave it. I renamed it to "str_list" locally.
This is now pushed.
Simon
prev parent reply other threads:[~2017-11-09 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 2:30 Simon Marchi
2017-10-30 2:33 ` Simon Marchi
2017-11-09 0:49 ` Simon Marchi [this message]
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=55f80ffd6b010b3bc1648112c188f2be@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.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).