Path: utzoo!attcan!uunet!mailrus!news-server.csri.toronto.edu!utgpu!watserv1!watcgl!cjwein
From: cjwein@watcgl.waterloo.edu (Chris J. Wein)
Newsgroups: comp.sys.ibm.pc.programmer
Subject: Re: Turbo C or MSC
Message-ID: <13776@watcgl.waterloo.edu>
Date: 14 Mar 90 14:58:51 GMT
References: <924@ns-mx.uiowa.edu>
Reply-To: cjwein@watcgl.waterloo.edu (Chris J. Wein)
Distribution: na
Organization: U. of Waterloo, Ontario
Lines: 19

In article <924@ns-mx.uiowa.edu> troj@icon.weeg.uiowa.edu () writes:
>In <10125@portia.Stanford.EDU>,  dma@nova.stanford.edu (Domingo Mihovilovic A)
>writes:
>
>If you do go the Turbo-C route, I'd strongly suggest you purchase 
>Turbo-C Professional, just for the sake of the debugger alone.  Turbo Debugger
>has saved me countless hours on single projects alone.
>
Just a note but recently, Borland and Watcom signed an agreement where
Turbo Debugger (v2.0) will be compatible with Watcom's C compiler.  There
will be a translation program which converts Watcom OBJ files to TDEBUGGER
compatible format.

Maybe this is a third option.  I have no personal experience with the Watcom
product but it's code generation is supposedly at or near the top in the
industry.

By the way, this is not a plug for the Watcom C compiler...just a tidbit of 
info FYI.