This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] A few ui_out formatting bugs with commands-on-breakpoints
- To: Jason Molenda <jason-swarelist at molenda dot com>
- Subject: Re: [RFA] A few ui_out formatting bugs with commands-on-breakpoints
- From: Jackie Smith Cashion <jsmith at redhat dot com>
- Date: Sun, 09 Sep 2001 09:45:59 -0500
- CC: GDB Patches <gdb-patches at sources dot redhat dot com>
- References: <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