Re: Eliminate tui_command_loop

[Pedro Alves <pedro@codesourcery.com>]

On Thursday 04 August 2011 21:17:40, Tom Tromey wrote:
> >>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:

> Pedro> -    tui_command_loop,
> 
> I think this was the last user of the command_loop_proc field.

Indeed.  Though,

/* Run the current command interpreter's main loop.  */
void
current_interp_command_loop (void)
{
  /* Somewhat messy.  For the moment prop up all the old ways of
     selecting the command loop.  `deprecated_command_loop_hook'
     should be deprecated.  */
  if (deprecated_command_loop_hook != NULL)
    deprecated_command_loop_hook ();
  else if (current_interpreter != NULL
	   && current_interpreter->procs->command_loop_proc != NULL)
    current_interpreter->procs->command_loop_proc (current_interpreter->data);
  else
    cli_command_loop ();
}

deprecated_command_loop_hook is used by insight.
Sounds like we could get rid of it, and make insight 
install a command_loop_proc callback in its interpreter.
(gdb/gdbtk/gdbtk-interp.c).

-- 
Pedro Alves