Date: Tue, 4 Apr 1995 20:16:03 -0700 (PDT)
From: ".ASM SoftWare Systems" <rdc AT freenet DOT vancouver DOT bc DOT ca>
Subject: Re: Questions
To: Charles Hunter <huntercr AT cs DOT purdue DOT edu>
Cc: Wayner <arthurto AT elmail DOT cc DOT purdue DOT edu>,
        djgpp mailing list <DJGPP AT sun DOT soe DOT clarkson DOT edu>

On Tue, 4 Apr 1995, Charles Hunter wrote:

> > 3) What is the editor of choice for all you DJGPPers?  I currently use 
> > qedit, but I dont' really like it for programming.  I'd like something 
> > that highlights the differnt parts of command different colors.  There is 
> > a program Zeus for Windows that I've tried, but I don't like switching 
> > back and forth and besides, my mouse locks up sometimes when I shell to 
> > DOS.  I'd also like something that will run a compiler with a command to 
> > see if I've made any mistakes.
> > 



                                                                        \
                                                               \O        \
                                                                     /    \
 At the risk of being told that TurboC and Qedit are "DEAD" ..      <      >
                                                                /    \    /
                                                               /O        /
                                                                        /
                                                            __
                                          Big enuf' Bill ?   /\
                                                            /
 



 I use Turbo C to develope and edit (use Help occasionally) DJGPP C programs.

 When I get so far I'll run it through Dj's C to see what it complains
about - maybe save some complaints and fix them .... Then back to TC ...


 I'll often #ifdef out __GNUC__ so it will run (and trace) and do some
preliminary testing under TurboC. Then back to gcc ...


 Now the GCC code is nearly ready to run (don't count chickens ... )
A last minute _FIX_ is done using Qedit - compile, execute, Yeah !


 The planned C interpretor will wreck this method - this is good ...

 Now if we only had an IDE (integrated development environment) where we
could edit, compile/Interpret, get context sensitive help ...
(Using all the GCC tools mushed together ;>  )
(With the editor in a seperate source so users can compile and link in 
thier favourite one if they don't want XYZ editor)