jlh@loral.UUCP (Physically Phffft) (01/10/89)
Ok, so now that Turbo C has been out for awhile and some of you have thoroughly used and abused it I'd like to ask a loaded question. I've been using Microsoft C (currently V5.1) for about a year now, and am familiar with it's quirks and features. Overall I like it but there are a few things I don't like about it (can you say disk hog?). Is it worth my time to convert to Turbo C? I'm especially interested in the debugger. Now a few caveats. First off, I'd like replies only from those of you who have actually used both enough to be familiar with them. None of this 'My hairdressers brothers wife loves ferbloop C" stuff. Second, I hate integrated environments like turbo pascal and quick C. Give me a command line any time. Third, I'm not worried about the $100 or so the compiler costs. I'm worried about the time spent to learn a new compiler, a new debugger, library conversion, code changes, etc. I figure it would take about a week to get familiar with the package, by that I mean I can go for a couple of hours without looking at a manual. Finally, I use C on a PC quite a bit in my job, so you can assume a pretty good level of knowledge on my part when you answer. Please answer by mail, if enough people are interested I'll summarize and post the results. Thanks for your time. Jim "Hollow chocolate has no calories" -- Jim Harkins jlh@loral.cts.com Loral Instrumentation, San Diego