Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] -stack-select-frame
Date: Fri, 17 Jun 2005 07:37:00 -0000	[thread overview]
Message-ID: <17074.32276.804157.95131@farnswood.snap.net.nz> (raw)
In-Reply-To: <20050617032149.GF17013@nevyn.them.org>

 > > -stack-info-frame hasn't been implemented yet (I've think we've been here
 > > before) but it would probably be quite easy to implement and I guess it
 > > could work like I've made -stack-select-frame without an argument work.
 > 
 > *snicker* that's what I get for reading the manual.  I assumed it was
 > implemented.
 > 
 > Maybe it is time to mark the unimplemented commands in the manual?

It _is_ documented as unimplemented in my copy.

   ...
 > If you're OK with only a literal "-stack-select-frame" providing the
 > frame information, how about implementing -stack-info-frame instead? 
 > The documentation for -stack-select-frame does not suggest the argument
 > is optional; we could make it mandatory.  It just seems cleaner to me
 > to have select be write-only and info be read-only.

The CLI command is both write-only and read-only.  Clearly there's no
 need to copy what might be existing bad practice and the command name
-stack-select-frame to provide frame information is unintuitive. I'll 
submit a patch to make -stack-info-frame do this.

Nick


  reply	other threads:[~2005-06-17  7:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-16  3:36 Nick Roberts
2005-06-16  4:42 ` Daniel Jacobowitz
2005-06-16  6:41   ` Nick Roberts
2005-06-16 13:21     ` Daniel Jacobowitz
2005-06-16 22:58       ` Nick Roberts
2005-06-16 23:20         ` Bob Rossi
2005-06-16 23:47         ` Daniel Jacobowitz
2005-06-17  3:07           ` Nick Roberts
2005-06-17  3:21             ` Daniel Jacobowitz
2005-06-17  7:37               ` Nick Roberts [this message]
2005-06-17 10:15                 ` Eli Zaretskii
2005-06-17 13:33                   ` Daniel Jacobowitz
2005-06-18  8:56                     ` Eli Zaretskii
2005-06-17  9:55               ` Eli Zaretskii
2005-06-17  9:46             ` Eli Zaretskii
2005-06-16 18:23 ` Eli Zaretskii
2005-06-16 20:15 ` Jason Molenda
2005-06-16 23:04   ` Nick Roberts
2005-06-16 23:30     ` Jason Molenda
2005-06-17  7:22       ` Nick Roberts
2005-06-17 13:30         ` Daniel Jacobowitz
2005-06-17 19:48         ` Jason Molenda
2005-06-17 22:35         ` Stan Shebs
2005-06-17 22:59           ` Daniel Jacobowitz
2005-06-17 23:31           ` Nick Roberts
     [not found] <1119003319.5434.ezmlm@sources.redhat.com>
2005-06-17 17:45 ` Jim Ingham

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=17074.32276.804157.95131@farnswood.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --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