From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [RFA 0/3] preparation for command constification; cleanup removal
Date: Mon, 11 Sep 2017 00:33:00 -0000 [thread overview]
Message-ID: <20170911003325.3765-1-tom@tromey.com> (raw)
In addition to the removal of cleanups, I've also long wanted to clean
up gdb by changing commands to take a "const char *".
With C++ this is simpler to do now, because we can use overloading to
minimize the neede code changes. To that end, the first patch in this
series renames some functions so we can take advantage of overloading
in the future.
The second patch is a minor constification patch in preparation for
the third patch.
The third patch changes extract_arg to return a std::string, which
allows for some cleanup removal.
Regression tested by the buildbot.
Tom
next reply other threads:[~2017-09-11 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 0:33 Tom Tromey [this message]
2017-09-11 0:33 ` [RFA 3/3] Make extract_arg return a std::string Tom Tromey
2017-09-11 19:52 ` Simon Marchi
2017-09-11 21:43 ` Tom Tromey
2017-09-11 0:33 ` [RFA 1/3] Rename _const functions to use overloading instead Tom Tromey
2017-09-11 19:16 ` Simon Marchi
2017-09-11 0:33 ` [RFA 2/3] Constify language_enum Tom Tromey
2017-09-11 19:17 ` 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=20170911003325.3765-1-tom@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/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