public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>, gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/testsuite: introduce parse_options procedure
Date: Tue, 26 May 2020 10:45:36 -0700	[thread overview]
Message-ID: <6d961a33-08f5-c5d0-c830-a6022e94696a@redhat.com> (raw)
In-Reply-To: <20200526130222.1956061-1-simon.marchi@polymtl.ca>

On 5/26/20 6:02 AM, Simon Marchi via Gdb-patches wrote:
> In the testsuite, I really like when procedures take optional arguments
> using shell-like options that start with dash (for example,
> gdb_test_multiple).  I think this leads to clearer code than using
> parameters with defaults value.

Is this sufficiently more robust than parse_args to warrant two variations
of a similar theme? Can they be merged into one implementation?

Keith


  reply	other threads:[~2020-05-26 17:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-26 13:02 Simon Marchi
2020-05-26 17:45 ` Keith Seitz [this message]
2020-05-26 18:19   ` Simon Marchi
2020-05-26 20:21     ` 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=6d961a33-08f5-c5d0-c830-a6022e94696a@redhat.com \
    --to=keiths@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).