Xref: news-dnh.mv.net comp.os.msdos.djgpp:2437
Path: news-dnh.mv.net!mv!news.sprintlink.net!simtel!news.kei.com!bloom-beacon.mit.edu!senator-bedfellow.mit.edu!space.mit.edu!davis
From: davis AT space DOT mit DOT edu (John E. Davis)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: IDE for DJGPP?
Date: 5 Oct 1995 15:15:34 GMT
Organization: Center for Space Research
Lines: 20
References: <DFEIDp DOT F1G AT jade DOT mv DOT net>
Reply-To: davis AT space DOT mit DOT edu
Nntp-Posting-Host: wiwaxia.mit.edu
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

On Sat, 23 Sep 1995 00:21:31 GMT, FRITZW AT URIACC DOT URI DOT EDU <FRITZW AT URIACC DOT URI DOT EDU> wrote:
 :    As for the GNU debugger, a glitzier interface would be a plus.  Right now,
 : it takes a lot longer to debug a GNU program then a Borland-compiled program,
 : because, although the GNU debugger compares in capabilities, it is very
 : difficult to learn (and I'm sick of typing 20 to 30 character variable and
 : function names, where's my point and click interface? :) Again, I'd be happy to
 : help out if I could, but somehow I don't think I'm quite skilled enough at
 : protected mode progrsamming to be of much use... :)
 
Strange.  I have had the exact opposite experience.  I am able to debug a
program much quicker using gdb that I am with Borland's debugger.  I have to
admit that I have only used the GNU debugger under Unix though.  I assume
that it works the same under MSDOS.

Regarding 20-30 character variable names, simply use TAB completion.  This
is MUCH quicker than clicking on the FILE menu and loading a particular .c
file, then searching for the word and clicking on it.

--John