Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Jan Vrany <jan.vrany@fit.cvut.cz>
Cc: gdb-patches <gdb-patches@sourceware.org>,  Tom Tromey <tom@tromey.com>
Subject: Re: [RFC] mi: add -a option to the "-data-disassemble" command
Date: Tue, 31 Jul 2018 15:48:00 -0000	[thread overview]
Message-ID: <87k1pb4dag.fsf@tromey.com> (raw)
In-Reply-To: <002372e4889b31236eb59b5a3414930cd0549346.camel@fit.cvut.cz> (Jan	Vrany's message of "Tue, 31 Jul 2018 11:23:05 +0100")

>>>>> "Jan" == Jan Vrany <jan.vrany@fit.cvut.cz> writes:

>> The indentation looked slightly off here.
>> It could just be how the patch looked here, but could you double-check
>> just in case?

Jan> My fault. My editor put 8 spaces instead of tab (\t) at the beginning of
Jan> my lines. Will fix. 

Thanks.  According to .dir-locals.el, tabs are fine, assuming things
line up properly.  (But there's been talk over the years of switching
purely to spaces, and IIRC using only spaces is also fine.)

Jan> I'm sorry I'm confused. Let me try to explain. There are (now) four forms:

Jan> 1a) -f filename -l linenum 
Jan> 1b) -f filename -l linenum -n lines 
Jan>  2) -s start-addr -e end-addr
Jan>  3) -a addr

Jan> Command  must have one of the above four forms, otherwise it's invalid. Each
Jan> "line" in the code above checks one of the above form (in order as written here). 
Jan> Note, that there's negation at the very beginning, so the condition holds 
Jan> if the command has none of the four forms. Seems "good" to me. Makes sense? 

Yes, thanks for explaining this.  I was misreading the new code here.

Jan> Now, it appears to me that first two lines can be merged as forms 1a and 1b differ only
Jan> in presence of lines. Also, I forgot to update the comment above. So, what about:
[...]

Thank you, that seems like a good improvement.

Tom


  reply	other threads:[~2018-07-31 15:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06  9:39 Jan Vrany
2018-07-06 12:37 ` Eli Zaretskii
2018-07-14 17:39   ` Jan Vrany
2018-07-14 18:27     ` Eli Zaretskii
2018-07-26 14:56       ` Jan Vrany
2018-07-26 17:47         ` Eli Zaretskii
2018-07-27  7:57           ` Jan Vrany
2018-07-30 15:05             ` Tom Tromey
2018-07-31 10:23               ` Jan Vrany
2018-07-31 15:48                 ` Tom Tromey [this message]
2018-07-31 20:35                   ` Jan Vrany
2018-08-09 20:47                     ` Tom Tromey
2018-08-10  8:29                       ` Jan Vrany
2018-08-10 13:22                         ` Tom Tromey
2018-08-10  8:30                       ` Jan Vrany
2018-08-10  9:47                         ` Pedro Alves
2018-08-10 10:28                           ` Jan Vrany
2018-08-10 10:41                             ` Pedro Alves
2018-08-14  9:16                               ` Jan Vrany
2018-08-14 13:57                                 ` Pedro Alves
2018-08-14 14:40                                 ` Eli Zaretskii

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=87k1pb4dag.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.vrany@fit.cvut.cz \
    /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