Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!zaphod.mps.ohio-state.edu!usc!ucsd!hub.ucsb.edu!6600sirt From: 6600sirt@ucsbuxa.ucsb.edu (Mike O'Brien) Newsgroups: comp.lang.c Subject: Re: Am I Happy with MS C 6.0? Message-ID: <5158@hub.ucsb.edu> Date: 8 May 90 07:01:18 GMT References: <8085@rouge.usl.edu> Sender: news@hub.ucsb.edu Reply-To: 6600sirt@ucsbuxa.ucsb.edu Distribution: usa Lines: 32 From article <8085@rouge.usl.edu>, by pcb@gator.cacs.usl.edu (Peter C. Bahrs): > Yes, the original problem, my biggest compaint about C 6.0 is not the > load time (that is a smaller gripe) but the time (almost 1 minute) > to compile a """"""" 1 """"""""""" line program !!!!!!!!! > > I like jazzy environments but I do not want things to get in my way: > I did not buy a new and improved product to have it compile SLOWER! > > Granted, I have a 16mhz PS/2 Model 70, but 5.1 quickC ran just fine. > I am not sure why I did not look into the performance aspect of the > upgrade before purchasing it. I will know better next time.... > .... and next time will probably be Win 3.0. I think you're missing the point. PWB is just a fancy front-end for the real compiler, CL. My computer is roughly comparable to yours, and it took me 59 seconds to compile and link "Hello World" through PWB. But it only takes me 12 seconds through CL. If you want to use MSC6, and you don't want to endure the wait, either use one or more of the tricks I gave you to speed up PWB, or don't use PWB! Finally, you surely must realize that "the performance aspect" can not be based solely on compile time. If you wanted a fast compile and didn't care about the quality of the resulting code, why didn't you buy Turbo C? Michael O'Brien 6600sirt@ucsbuxa.ucsb.edu