Path: utzoo!attcan!uunet!zephyr.ens.tek.com!uw-beaver!mit-eddie!wuarchive!mailrus!ncar!boulder!gore!jacob
From: jacob@gore.com (Jacob Gore)
Newsgroups: comp.sys.next
Subject: Re: A plea for a Structured Objective-C code browser in 2.0
Message-ID: <130107@gore.com>
Date: 27 Sep 90 19:45:20 GMT
References: <27092@boulder.Colorado.EDU>
Reply-To: jacob@gore.com (Jacob Gore)
Organization: Gore Enterprises
Lines: 27

/ comp.sys.next / chase@boulder.Colorado.EDU (A. Chase Turner) / Sep 27, 1990 /
> I am finding myself completely dismayed at the disjoint cycle of 
> development I must waddle through:

> 	- Write and modify code with Edit.
> 	- Compile till gnu pukes.
> 	- Correct syntax by walking through line numbers returned by 
> 	   the compilier;  associate line number with code using 
> 	   Edit's Select Line option.
> 	- Syntax is okay but application is not behaving correctly -- 
> 	   need to step through the code using gdb -- gave up 
> 	   because it is too primative of a user interface
> 	- Finally laced my code with printfs and successfully debugged 
> 	   my application code....

Yuck!  You're using the wrong tools.  Use Emacs.  Write (or modify) your
code, compile it (M-x compile), step through syntax errors (C-x `); debug
it with gdb mode (M-x gdb), which shows the source you're stepping through
in a window to the actual source, opening files as needed (can even do some
editing right on the spot!).

Sure, a class browser would be nice.  But you're making your life much
harder than it has to be.

Jacob
--
Jacob Gore		Jacob@Gore.Com			boulder!gore!jacob