Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jackie Smith Cashion <jsmith@redhat.com>
To: Jason Molenda <jason-swarelist@molenda.com>
Cc: GDB Patches <gdb-patches@sources.redhat.com>
Subject: Re: [RFA] A few ui_out formatting bugs with commands-on-breakpoints
Date: Sun, 09 Sep 2001 07:51:00 -0000	[thread overview]
Message-ID: <3B9B80A7.D1582D6D@redhat.com> (raw)
In-Reply-To: <20010907234014.A10697@shell17.ba.best.com>

Jason Molenda wrote:
> 
> My only concern is that I'm unfamiliar with the UI_OUT suite of
> functions.  Are certain ui_out functions are preferred over others?
> For instance, we have "end" printed out by both ui_out_field_string()
> and by ui_out_text().  I removed the first occurrence in each case,
> but who knows, maybe there's a reason to do it the other way.  From
> what I can tell in the uiout doco, it's six of one and half a dozen
> of the other.

I was uncertain about which flavor of ui_out to use also. From
Fernando's explanation and an off list comment I received from someone
else I learned that the really important information should be output
via ui_out_field_*. ui_out_text and it's derivative ui_out_spaces are
just for making the output "pretty" in the generic command line form of
GDB. GUI front ends to GDB typically write the output from
ui_out_field_* to a window but may completely ignore the output from
ui_out_text and ui_out_spaces.

This was not obvious to me when reviewing the implementation of the
UI_OUT functions.

-- 

Jackie Smith Cashion


  parent reply	other threads:[~2001-09-09  7:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-07 23:40 Jason Molenda
2001-09-08 11:06 ` Fernando Nasser
2001-09-09  7:51 ` Jackie Smith Cashion [this message]
2001-09-09  9:21   ` 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=3B9B80A7.D1582D6D@redhat.com \
    --to=jsmith@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jason-swarelist@molenda.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