Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [RFA 5/5] Use ui_out_emit_list
Date: Tue, 18 Apr 2017 18:44:00 -0000	[thread overview]
Message-ID: <1a1902d6-65c0-7ab4-2be9-ed1357f04dac@redhat.com> (raw)
In-Reply-To: <20170414022337.28368-6-tom@tromey.com>

On 04/14/2017 03:23 AM, Tom Tromey wrote:
> This changes some spots to use ui_out_emit_list.  This only touches
> "easy" cases, where the cleanup was used in a block-structured way.
> There's also one more use of ui_out_emit_tuple in here.
> 
> ChangeLog
> 2017-04-13  Tom Tromey  <tom@tromey.com>
> 
> 	* mi/mi-cmd-file.c (mi_cmd_file_list_shared_libraries): Use
> 	ui_out_emit_list.
> 	* stack.c (print_frame): Use ui_out_emit_list.
> 	* mi/mi-symbol-cmds.c (mi_cmd_symbol_list_lines): Use
> 	ui_out_emit_list.
> 	* mi/mi-main.c (print_one_inferior)
> 	(mi_cmd_data_list_register_names)
> 	(mi_cmd_data_list_register_values, mi_cmd_list_features)
> 	(mi_cmd_list_target_features, mi_cmd_trace_frame_collected): Use
> 	ui_out_emit_list.
> 	* mi/mi-interp.c (mi_on_normal_stop_1): Use ui_out_emit_list.
> 	(mi_output_solib_attribs): Use ui_out_emit_list,
> 	ui_out_emit_tuple.
> 	* mi/mi-cmd-var.c (varobj_update_one): Use ui_out_emit_list.
> 	* mi/mi-cmd-stack.c (mi_cmd_stack_list_frames)
> 	(mi_cmd_stack_list_args, list_args_or_locals): Use
> 	ui_out_emit_list.
> 	* disasm.c (do_assembly_only): Use ui_out_emit_list.
> 	* breakpoint.c (print_solib_event, output_thread_groups): Use
> 	ui_out_emit_list.

LGTM.

Thanks,
Pedro Alves


  reply	other threads:[~2017-04-18 18:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14  2:23 [RFA 0/5] some cleanup removal for ui_out Tom Tromey
2017-04-14  2:23 ` [RFA 2/5] More uses of ui_out_emit_tuple Tom Tromey
2017-04-18 18:42   ` Pedro Alves
2017-04-19  2:42     ` Tom Tromey
2017-04-19  9:39       ` Pedro Alves
2017-04-14  2:23 ` [RFA 5/5] Use ui_out_emit_list Tom Tromey
2017-04-18 18:44   ` Pedro Alves [this message]
2017-04-14  2:23 ` [RFA 3/5] Use ui_out_emit_tuple in tracepoint.c Tom Tromey
2017-04-18 18:43   ` Pedro Alves
2017-04-14  2:24 ` [RFA 1/5] Use ui_out_emit_tuple Tom Tromey
2017-04-18 18:42   ` Pedro Alves
2017-04-14  2:42 ` [RFA 4/5] Use ui_out_emit_tuple in more places in MI Tom Tromey
2017-04-18 18:44   ` Pedro Alves
2017-04-22 15:44 ` [RFA 0/5] some cleanup removal for ui_out Tom Tromey
2017-04-27 14:51   ` Simon Marchi
2017-04-27 21:23     ` Tom Tromey

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=1a1902d6-65c0-7ab4-2be9-ed1357f04dac@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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