From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] print arrays with indexes
Date: Sun, 18 Sep 2005 03:37:00 -0000 [thread overview]
Message-ID: <uoe6r59n4.fsf@gnu.org> (raw)
In-Reply-To: <20050917215138.GB2496@adacore.com> (message from Joel Brobecker on Sat, 17 Sep 2005 14:51:38 -0700)
> Date: Sat, 17 Sep 2005 14:51:38 -0700
> From: Joel Brobecker <brobecker@adacore.com>
>
> > Then doesn't it make sense to agree on the interface first? :-)
>
> Right! I just wanted to hear a few other opinions to choose.
> Perhaps Eli and/or Mark would like to comment?
>
> In any case:
>
> > You suggested on/off/auto and a separate threshold. Jim suggested
> > on/off/threshold. I prefer on/off/threshold of those two options,
> > although it may be a bit tricky to get GDB to handle that correctly.
> > Want to give it a try, or continue discussing alternatives?
>
> I'm willing to give it a try. I couldn't find a mechanism in our
> "set/show" machinery that handled something like this, though.
> Unless I missed it, that's something I'll need to add too.
I don't see any disadvantages to the on/off/auto+threshold method that
would justify yet another add_* interface. Can someone please tell
why is that a good idea?
next prev parent reply other threads:[~2005-09-18 3:37 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 20:20 [RFC/RFA] " Joel Brobecker
2005-09-06 20:57 ` Daniel Jacobowitz
2005-09-07 5:40 ` Joel Brobecker
2005-09-07 13:23 ` Daniel Jacobowitz
2005-09-07 20:24 ` Joel Brobecker
2005-09-14 17:13 ` [RFA] " Joel Brobecker
2005-09-17 20:49 ` Daniel Jacobowitz
2005-09-17 21:51 ` Joel Brobecker
2005-09-17 22:07 ` Daniel Jacobowitz
2005-09-18 3:37 ` Eli Zaretskii [this message]
2005-09-18 3:46 ` Daniel Jacobowitz
2005-09-18 5:41 ` Joel Brobecker
2005-09-18 19:08 ` Eli Zaretskii
2005-09-18 19:19 ` Daniel Jacobowitz
2005-09-18 20:05 ` Eli Zaretskii
2005-09-20 7:31 ` Joel Brobecker
2005-09-20 19:18 ` Eli Zaretskii
2005-09-20 19:31 ` Joel Brobecker
2005-09-20 19:33 ` Daniel Jacobowitz
2005-09-20 19:39 ` Joel Brobecker
2005-09-21 3:44 ` Eli Zaretskii
2005-09-22 16:47 ` Joel Brobecker
2005-09-26 1:23 ` Daniel Jacobowitz
2005-09-27 1:04 ` Joel Brobecker
2005-10-02 22:42 ` Daniel Jacobowitz
2005-10-03 6:17 ` Joel Brobecker
2005-10-03 15:50 ` Daniel Jacobowitz
2005-10-03 21:23 ` Joel Brobecker
2005-10-04 7:02 ` Joel Brobecker
2005-10-04 7:41 ` Joel Brobecker
2005-09-21 3:44 ` Eli Zaretskii
2005-09-18 8:53 ` Mark Kettenis
2005-09-18 19:10 ` Eli Zaretskii
2005-09-07 20:39 ` [RFC/RFA] " Jim Blandy
2005-09-07 21:41 ` Joel Brobecker
2005-09-09 19:14 ` Jim Blandy
2005-09-06 21:45 ` Jim Blandy
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=uoe6r59n4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.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