From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/5] Teach gdb::option about string options
Date: Fri, 28 Jun 2019 15:11:00 -0000 [thread overview]
Message-ID: <87woh5zqw1.fsf@tromey.com> (raw)
In-Reply-To: <20190627191427.20742-4-palves@redhat.com> (Pedro Alves's message of "Thu, 27 Jun 2019 20:14:25 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> This commit adds support for string options, mapped to var_string.
Pedro> For now, a string is parsed up until the first whitespace. I imagine
Pedro> that we'll need to add support for quoting so that we could do:
Pedro> (gdb) cmd -option 'some -string'
Pedro> without gdb confusing the "-string" for an option.
Pedro> This doesn't seem important for pipe, so I'm leaving it for another
Pedro> day.
I wonder if we should file bugs for known holes like this.
On the one hand it seems nice to write down what we know.
On the other hand, maybe nobody will ever look at these.
Pedro> + /* Disable the copy constructor. */
Pedro> + option_def_and_value (const option_def_and_value &rval) = delete;
I wonder if it makes sense to disable operator= as well.
Tom
next prev parent reply other threads:[~2019-06-28 15:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 19:14 [PATCH 0/5] pipe command completer, and " Pedro Alves
2019-06-27 19:14 ` [PATCH 3/5] Teach gdb::option about " Pedro Alves
2019-06-28 15:11 ` Tom Tromey [this message]
2019-06-27 19:14 ` [PATCH 5/5] pipe command completer Pedro Alves
2019-06-28 15:16 ` Tom Tromey
2019-07-03 16:28 ` Pedro Alves
2019-06-27 19:14 ` [PATCH 2/5] Make gdb::option::complete_options save processed arguments too Pedro Alves
2019-06-27 19:14 ` [PATCH 1/5] Fix test_gdb_complete_tab_multiple race Pedro Alves
2019-06-27 19:14 ` [PATCH 4/5] Fix latent bug in test_gdb_complete_cmd_multiple Pedro Alves
2019-06-28 14:53 ` Tom Tromey
2019-06-28 14:56 ` Pedro Alves
2019-06-28 15:46 ` Tom Tromey
2019-06-28 15:16 ` [PATCH 0/5] pipe command completer, and string options Tom Tromey
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=87woh5zqw1.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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