Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Aaron Gamble <agamble@google.com>, gdb-patches@sourceware.org
Subject: Re: [patch] info threads sort by name and name regex matching
Date: Thu, 23 Aug 2012 16:00:00 -0000	[thread overview]
Message-ID: <87pq6hppiz.fsf@fleche.redhat.com> (raw)
In-Reply-To: <m3boi2ld2u.fsf@redhat.com> (Sergio Durigan Junior's message of	"Wed, 22 Aug 2012 20:30:17 -0300")

Sergio> Why not `-r regex'?  I think it would be more clear.

Me too.

Sergio> Other commands (`sharedlibrary', `info variables', etc) take a regex as
Sergio> their first argument, without requiring a modifier like `-r'.  If the
Sergio> "pipe" patch were already in, this alphabetical sorting would not be
Sergio> needed...  Anyway, just thinking here.

Piping is nice but I think it is also good to have options for common
cases.

Sergio> I guess Tom did not suggest this because of performance per se, but
Sergio> rather because if you have to make a list in GDB then it is already a
Sergio> convention to use VEC for these things.

Yeah.  I thought it would make the code simpler.

Tom


  reply	other threads:[~2012-08-23 16:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 21:19 Aaron Gamble
2012-08-22 10:06 ` Abid, Hafiz
2012-08-22 17:15 ` Eli Zaretskii
2012-08-22 18:52 ` Tom Tromey
2012-08-22 22:37   ` Aaron Gamble
2012-08-22 23:30     ` Sergio Durigan Junior
2012-08-23 16:00       ` Tom Tromey [this message]
2012-08-24  1:09         ` Aaron Gamble
2012-08-24 17:58           ` Tom Tromey
2012-08-24 22:23             ` Aaron Gamble
2012-08-24 22:32               ` Sergio Durigan Junior
2012-08-24 23:21                 ` Aaron Gamble
2012-08-24 23:28                 ` Aaron Gamble
2012-08-25  3:12                   ` Sergio Durigan Junior

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=87pq6hppiz.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=agamble@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@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