Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!mit-eddie!rutgers!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!dd26+
From: dd26+@andrew.cmu.edu (Douglas F. DeJulio)
Newsgroups: comp.sys.next
Subject: Re: A plea for a Structured Objective-C code browser in 2.0
Message-ID: <8b0fl7i00VI8F4JDp4@andrew.cmu.edu>
Date: 28 Sep 90 02:58:15 GMT
References: <27092@boulder.Colorado.EDU>
Organization: Chemistry, Carnegie Mellon, Pittsburgh, PA
Lines: 27
In-Reply-To: <27092@boulder.Colorado.EDU>

chase@boulder.Colorado.EDU (A. Chase Turner) writes:
> I am listing my experience in programming environments -- in 
> descending order of preference:
> 
>         ParcPlace's ObjectWorks -- both Smalltalk and C++
>         Symbolic's Genera programming environment
>         LightSpeed C on the Mac
>         Sun's dbxtool (for C and C++) 
> 
> I rate NeXT's gdb and Edit at the very bottom.

You are making a mistake.  You should use gnu-emacs, and use gdb-mode.
You're not using the software that's available to you.  With the
emacs/gdb combination, you can have a source file in one windown and
the debugger in another, and as you step through the program with the
debugger, a little arrow shows you where you are in the source.  You
can go to the source and hit a key, and the debugger will set a
breakpoint there.  There are lots of nifty features you could and
should be using.

From within gnu-emacs you can compile.  Then, when the compiler shows
errors, you can hit the "show me the next error" key combination and
the apropriate source file will be opened, and the cursor will be
placed on the offending line.  Use the tools you've already got!
-- 
Doug DeJulio
dd26@andrew.cmu.edu