GNUtify TUI code, enable TUI

GNUtify TUI code, enable TUI

[Andrew Cagney]

Hello,

I think its time to GNUtify the TUI code.  Actually, the code should 
have been GNUtifyed before that faitful first commit, however now is 
better late than never :-)  (Stephane's been careful to ensure that any 
new code is GNUtiful, this will fix the old code).  As for building 
theTUI by default, its been on the things-to-do-today list for too long 
:-(  So the plan is:

~2004-01-10: Rename the files/functions.  Mindless, tedious, but 
relatively "obvious".

~2004-01-17: Enable the TUI by default.

comments,
Andrew

Re: GNUtify TUI code, enable TUI

[Daniel Jacobowitz]

On Mon, Jan 05, 2004 at 03:19:15PM -0500, Andrew Cagney wrote:
> Hello,
> 
> I think its time to GNUtify the TUI code.  Actually, the code should 
> have been GNUtifyed before that faitful first commit, however now is 
> better late than never :-)  (Stephane's been careful to ensure that any 
> new code is GNUtiful, this will fix the old code).  As for building 
> theTUI by default, its been on the things-to-do-today list for too long 
> :-(  So the plan is:
> 
> ~2004-01-10: Rename the files/functions.  Mindless, tedious, but 
> relatively "obvious".
> 
> ~2004-01-17: Enable the TUI by default.

Sounds good to me, Debian's been using the TUI for a year or so now. 

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: GNUtify TUI code, enable TUI

[Eli Zaretskii]

> Date: Mon, 05 Jan 2004 15:19:15 -0500
> From: Andrew Cagney <cagney@gnu.org>
> 
> I think its time to GNUtify the TUI code.

What does that mean?  I'm not familiar with the term.

> ~2004-01-17: Enable the TUI by default.

On all platforms?  It probably won't work for DJGPP at least.

Re: GNUtify TUI code, enable TUI

[Andrew Cagney]

>> Date: Mon, 05 Jan 2004 15:19:15 -0500
>> From: Andrew Cagney <cagney@gnu.org>
>> 
>> I think its time to GNUtify the TUI code.
> 
> 
> What does that mean?  I'm not familiar with the term.

Update the code so that it complies with GNU coding standards - make it 
GNUtiful (groan).  At present the code is not very GNU coding standard 
like :-(.

>> ~2004-01-17: Enable the TUI by default.
> 
> 
> On all platforms?  It probably won't work for DJGPP at least.

As many as possible.  (looking at configure.in) It would be made 
conditional on there being a curses library (which I think precludes DJGPP).

Andrew

Re: GNUtify TUI code, enable TUI

[Eli Zaretskii]

> Date: Tue, 06 Jan 2004 16:54:39 -0500
> From: Andrew Cagney <cagney@gnu.org>
> 
> (looking at configure.in) It would be made conditional on there
> being a curses library (which I think precludes DJGPP).

Not necessarily: there's a port of PDCurses.  I will look into using
that to get a TUI build when I have time.

One thing I'd request to change in preparation for making TUI the
default is to rename some of the files in gdb/tui/ so that they don't
conflict after 8+3 butchery (see fnchange.lst or run doschk).
Renaming via fnchange.lst is okay for files that aren't used in the
DJGPP build, but it's a darn PITA for those that need to be compiled,
since Makefile's etc. need to be edited as well, which fnchange.lst
doesn't do.

Re: GNUtify TUI code, enable TUI

[Andrew Cagney]

> Date: Tue, 06 Jan 2004 16:54:39 -0500
>> From: Andrew Cagney <cagney@gnu.org>
>> 
>> (looking at configure.in) It would be made conditional on there
>> being a curses library (which I think precludes DJGPP).
> 
> 
> Not necessarily: there's a port of PDCurses.  I will look into using
> that to get a TUI build when I have time.
> 
> One thing I'd request to change in preparation for making TUI the
> default is to rename some of the files in gdb/tui/ so that they don't
> conflict after 8+3 butchery (see fnchange.lst or run doschk).
> Renaming via fnchange.lst is okay for files that aren't used in the
> DJGPP build, but it's a darn PITA for those that need to be compiled,
> since Makefile's etc. need to be edited as well, which fnchange.lst
> doesn't do.

Yes, good point.  I'll toss in an extra ~week, and post draft new names 
so people can pick on them :-)

Andrew

Re: GNUtify TUI code, enable TUI

[Eli Zaretskii]

> Date: Wed, 07 Jan 2004 09:58:47 -0500
> From: Andrew Cagney <cagney@gnu.org>
> 
> I'll toss in an extra ~week, and post draft new names so people can
> pick on them :-)

Thanks!

Re: GNUtify TUI code, enable TUI

[Stephane Carrez]

Hi!

Andrew Cagney wrote:
> Hello,
> 
> I think its time to GNUtify the TUI code.  Actually, the code should 
> have been GNUtifyed before that faitful first commit, however now is 
> better late than never :-)  (Stephane's been careful to ensure that any 
> new code is GNUtiful, this will fix the old code).  As for building 
> theTUI by default, its been on the things-to-do-today list for too long 
> :-(  So the plan is:
> 
> ~2004-01-10: Rename the files/functions.  Mindless, tedious, but 
> relatively "obvious".
> 
> ~2004-01-17: Enable the TUI by default.
> 
> comments,
> Andrew
> 

Great!  So you plan to have this for 6.1?

This reminds me some work I did last summer on TUI register window to
cleanup the code and use the gdb new register API (and fix some bunch
of problems...).  Not committed because... lack of time? Valentin's birth?

There is also this TUI testsuite I wrote.  It works but for some
reasons sometimes expect fails to recognize the output (:-

I'll try to resurect my TUI reg fixes...

	Stephane

-- 
         Home                           Office
E-mail: stcarrez@nerim.fr              Stephane.Carrez@solsoft.com
WWW:    http://stcarrez.nerim.net      http://www.solsoft.com
         Free the Software!             Security Policy Management

Re: GNUtify TUI code, enable TUI

[Daniel Jacobowitz]

On Thu, Jan 08, 2004 at 09:26:33PM +0100, Stephane Carrez wrote:
> Hi!
> 
> Andrew Cagney wrote:
> >Hello,
> >
> >I think its time to GNUtify the TUI code.  Actually, the code should 
> >have been GNUtifyed before that faitful first commit, however now is 
> >better late than never :-)  (Stephane's been careful to ensure that any 
> >new code is GNUtiful, this will fix the old code).  As for building 
> >theTUI by default, its been on the things-to-do-today list for too long 
> >:-(  So the plan is:
> >
> >~2004-01-10: Rename the files/functions.  Mindless, tedious, but 
> >relatively "obvious".
> >
> >~2004-01-17: Enable the TUI by default.
> >
> >comments,
> >Andrew
> >
> 
> Great!  So you plan to have this for 6.1?
> 
> This reminds me some work I did last summer on TUI register window to
> cleanup the code and use the gdb new register API (and fix some bunch
> of problems...).  Not committed because... lack of time? Valentin's birth?
> 
> There is also this TUI testsuite I wrote.  It works but for some
> reasons sometimes expect fails to recognize the output (:-
> 
> I'll try to resurect my TUI reg fixes...

That'd be great.  Let me know if you want me to take a shot at the
expect problems, I've had some practice with that.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: GNUtify TUI code, enable TUI

[Andrew Cagney]

>> Hi!
>> 
>> Andrew Cagney wrote:
>> Hello,
>> 
>> I think its time to GNUtify the TUI code.  Actually, the code should have been GNUtifyed before that faitful first commit, however now is better late than never :-)  (Stephane's been careful to ensure that any new code is GNUtiful, this will fix the old code).  As for building theTUI by default, its been on the things-to-do-today list for too long :-(  So the plan is:
>> 
>> ~2004-01-10: Rename the files/functions.  Mindless, tedious, but relatively "obvious".
>> 
>> ~2004-01-17: Enable the TUI by default.
>> 
>> comments,
>> Andrew


> 
> 
> Great!  So you plan to have this for 6.1?

Yep, that's the intent.  I'm hoping that this time I've started the 
process early enough to make the branch date ...

> This reminds me some work I did last summer on TUI register window to
> cleanup the code and use the gdb new register API (and fix some bunch
> of problems...).  Not committed because... lack of time? Valentin's birth?
> 
> There is also this TUI testsuite I wrote.  It works but for some
> reasons sometimes expect fails to recognize the output (:-
> 
> I'll try to resurect my TUI reg fixes...

ya!

Andrew