From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: <gdb-patches@sourceware.org>, Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: [PATCH 3/3] Remove usage of VEC(char_ptr) in gdbscm_parse_function_args
Date: Sun, 01 Apr 2018 16:29:00 -0000 [thread overview]
Message-ID: <87370eevq4.fsf@tromey.com> (raw)
In-Reply-To: <1521667509-303-3-git-send-email-simon.marchi@ericsson.com> (Simon Marchi's message of "Wed, 21 Mar 2018 17:25:09 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@ericsson.com> writes:
Simon> From: Simon Marchi <simon.marchi@polymtl.ca>
Simon> This is a straightforward replacement, no change in behavior are
Simon> intended/expected.
Simon> This is the last usage of VEC(char_ptr), so it can now be removed.
I think perhaps the char_ptr typedef could be removed now too.
Tom
next prev parent reply other threads:[~2018-04-01 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 21:25 [PATCH 1/3] Use std::vector in uploaded_tp Simon Marchi
2018-03-21 21:25 ` [PATCH 3/3] Remove usage of VEC(char_ptr) in gdbscm_parse_function_args Simon Marchi
2018-04-01 16:29 ` Tom Tromey [this message]
2018-04-01 18:25 ` Simon Marchi
2018-04-02 2:23 ` Tom Tromey
2018-03-21 21:25 ` [PATCH 2/3] Use std::vector and std::string instead of VEC(char_ptr) in gdbserver tdesc Simon Marchi
2018-03-30 21:20 ` [PATCH 1/3] Use std::vector in uploaded_tp Simon Marchi
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=87370eevq4.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).