Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Stephane Carrez <Stephane.Carrez@worldnet.fr>,
	Elena Zannoni <ezannoni@cygnus.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Cleanup tui/tui-file.[ch]
Date: Tue, 17 Jul 2001 13:40:00 -0000	[thread overview]
Message-ID: <15188.42006.287402.818893@krustylu.cygnus.com> (raw)
In-Reply-To: <3B54896A.4070205@cygnus.com>

Andrew Cagney writes:
 > 
 > > Ah!!!  The marvellous -Werror that I'm currently figthing with in ChorusOS
 > > to remove all our warnings..... ... ...
 > > 
 > > 
 > >> I think it is because you removed the #include "tuiIO.h".
 > >> 
 > >> Can I put it back?
 > > 
 > > 
 > > Sure!
 > 
 > 
 > Hmm, is tui-file now only needed when the TUI is included?
 > 
 > 	Andrew


Looks that way. Another thought is that now we can get rid
of some the *_base_* functions that were added for the TUI. For
instance, print_frame_info_base and print_frame_info.

From the HP merge changelog (1998), just random grepping for _base:

	* source.c :(print_source_lines): Rename to
	print_source_lines_base and make static; formatting.
	(print_source_lines): New function.

	* stack.c (down_silently_base, up_silently_base,
 	args_plus_locals_info, print_frame_info_base,
 	print_stack_frame_base, print_stack_frame_base_stub): Declare.
	(print_stack_frame_stub): New version created, old version renamed
 	to show_and_print_stack_frame_base_stub.
	(print_stack_frame_base_stub, print_only_stack_frame_stub,
 	show_and_print_stack_frame, print_only_stack_frame,
 	stack_publish_stopped_with_no_frame, print_frame_info,
 	show_stack_frame, backtrace_full_command, args_plus_locals_info,
	select_and_print_frame, select_and_maybe_print_frame,
	current_frame_command, func_command): New functions.
	(backtrace_command): New function, old renamed to
	backtrace_command_1.
	(print_block_frame_locals, print_frame_local_vars): Additional
	parameter, number of tabs.
	(up_silently_command): New function, old renamed to
	up_silently_command_base.
	(down_silently_command): New function, old renamed to
	down_silently_base.

Elena


  reply	other threads:[~2001-07-17 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3B536421.C4F0E04D@worldnet.fr>
2001-07-16 15:57 ` Andrew Cagney
2001-07-17 10:19 ` Elena Zannoni
     [not found]   ` <3B548825.773525AC@worldnet.fr>
2001-07-17 11:52     ` Andrew Cagney
2001-07-17 13:40       ` Elena Zannoni [this message]
2001-07-17 13:23     ` Elena Zannoni

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=15188.42006.287402.818893@krustylu.cygnus.com \
    --to=ezannoni@cygnus.com \
    --cc=Stephane.Carrez@worldnet.fr \
    --cc=ac131313@cygnus.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