Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!polyslo!jdudeck
From: jdudeck@polyslo.CalPoly.EDU (John R. Dudeck)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Wanted: good C environment
Keywords: Turbo C, Microsoft C
Message-ID: <25cfc2dc.4a37@polyslo.CalPoly.EDU>
Date: 7 Feb 90 06:40:28 GMT
References: <51736@bbn.COM> <25CF28FA.13935@maccs.dcss.mcmaster.ca>
Reply-To: jdudeck@polyslo.CalPoly.EDU (John R. Dudeck)
Organization: Cal Poly State University -- San Luis Obispo
Lines: 18


Perhaps I am a little less gimmick-prone than a lot of programmers.  I
just use my favorite editor (Logitech Point), and make.  Make invokes
the MS C compiler as needed.  I use code view for debugging.

In order to keep from retyping commands when I go between them, I 
use ndosedit, which allows me to recall the command line.  
(4DOS, Anarkey, ced, and others will do the same).

I find that I prefer this arrangement over Quick C.  The only disadvantage
is that it doesn't point to syntax errors in the editor after I compile.
But Point will let me have the listing open in one window and the source
in the another, which gives me more information anyway.  As far as I am
concerned, the advantages of the Point editor for speed and ease of use
outweigh the advantages of Quick C or Turbo C.  I can see no disadvantages
to my approach in terms of keystrokes, mental effort, or elapsed time
to get a debugged .exe file.


-- 
John Dudeck                           "You want to read the code closely..." 
jdudeck@Polyslo.CalPoly.Edu             -- C. Staley, in OS course, teaching 
ESL: 62013975 Tel: 805-545-9549          Tanenbaum's MINIX operating system.