Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jackie Smith Cashion <jsmith@redhat.com>
To: Fernando Nasser <fnasser@redhat.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: RFA: "show user" output
Date: Fri, 07 Sep 2001 11:04:00 -0000	[thread overview]
Message-ID: <3B990AFF.2B2AD149@redhat.com> (raw)
In-Reply-To: <3B98D43B.777559DD@redhat.com>

The output looks okay when I run the modified GDB. I must admit it's not
clear to me which ui_out function to use for which purpose. Here's how I
made my decisions:

while: I removed the call to ui_out_text since it does not output the
rest of the "while" command line.

while end: It is important to output the indenting spaces before the
keyword, so I removed the call to ui_out_field_string that came before
the ui_out_spaces.

if: I removed the call to ui_out_text since it does not output the rest
of the "if" command line.

else: Since ui_out_text had been used above to output "end" which like
"else" has no command line arguments, I kept the call to ui_out_text
here.

if end: I removed the call to ui_out_field_string that came before the
ui_out_spaces.

I guess the question is whether ui_out_text or ui_out_field_string
should be used to print a simple string with no additional arguments. Is
there a general rule? 

Jackie


Fernando Nasser wrote:
> 
> Have you checked the MI output before and after your patch?
> 
> In particular, this bit suggests that in this last chunk you've removed
> the
> "good" else/end and left the "bad" ones ;-)
> 
> > *************** print_command_lines (struct ui_out *uiou
> > *** 197,208 ****
> >             {
> >               if (depth)
> >                 ui_out_spaces (uiout, 2 * depth);
> > -             ui_out_field_string (uiout, NULL, "else");
> >               ui_out_text (uiout, "else\n");
> >               print_command_lines (uiout, list->body_list[1], depth + 1);
> >             }
> >
> > -         ui_out_field_string (uiout, NULL, "end");
> >           if (depth)
> >             ui_out_spaces (uiout, 2 * depth);
> >           ui_out_text (uiout, "end\n");
> > --- 194,203 ----
> 
> Regards,
> Fernando
> 
> --
> Fernando Nasser
> Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
> 2323 Yonge Street, Suite #300
> Toronto, Ontario   M4P 2C9

-- 

Jackie Smith Cashion

email:  jsmith@redhat.com
phone:  931 438 2432


  reply	other threads:[~2001-09-07 11:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-06 14:58 Jackie Smith Cashion
2001-09-07  7:09 ` Fernando Nasser
2001-09-07 11:04   ` Jackie Smith Cashion [this message]
2001-09-08 11:18     ` Fernando Nasser
2001-09-08 19:13       ` Jackie Smith Cashion
2001-09-09  8:15         ` Fernando Nasser
2001-09-09 10:20           ` Jackie Smith Cashion
2001-09-10  8:33             ` Fernando Nasser
2001-09-10  7:57           ` Andrew Cagney
2001-09-10  8:35             ` Fernando Nasser
2001-09-10  8:54               ` Andrew Cagney

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=3B990AFF.2B2AD149@redhat.com \
    --to=jsmith@redhat.com \
    --cc=fnasser@redhat.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