Path: utzoo!attcan!uunet!lll-winken!ames!mailrus!cornell!uw-beaver!uw-june!robertb
From: robertb@june.cs.washington.edu (Robert Bedichek)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C 2.0 and EMS
Message-ID: <6957@june.cs.washington.edu>
Date: 17 Jan 89 01:45:15 GMT
References: <31050@tut.cis.ohio-state.edu> <597@dms.UUCP>
Reply-To: robertb@uw-june.UUCP (Robert Bedichek)
Organization: U of Washington, Computer Science, Seattle
Lines: 28

I called Borland a few days ago to ask what serial number of TC 2.0 had
the latest bug fixes.  The guy said "There are no known bugs in 2.0".
Wow.  Really?  I used it intensively for about a week and didn't
run into a single bug, not even in the debugger.  Debuggers in my
experience are usually the buggiest tool in a development environment.

Then I read this:

"<stuff about how great TC 2.0 is deleted>
">
">(I am not saying all their code is bug free, but what code is?? :>} )
">-- 
">Jim Morris.         			 morris@dms.UUCP or weitek!dms!morris
">           Atari Games Corporation, Sycamore Drive, Milpitas CA 95035.
">       (Arcade Video Game Manufacturer, NOT Atari Corp. ST manufacturer).
"> Any opinions expressed are probably my own, and not those of Atari Games Corp.

So, my question: Does anyone know of any bugs in TC 2.0?  The only
thing that comes close is that the if your program runs in graphics
mode and you use the debugger, the screen can get messed up if you
don't do something special.  I read about this special thing in the
manual but haven't done it yet.  So I don't consider this a bug
(its a limitation that they tell you about and how to work-around).

Rob Bedichek

  .. "Code to live.
      Live to Code."