Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!husc6!sri-unix!sri-spam!ames!ucbcad!zen!ucbvax!jade!violet.berkeley.edu!ephram
From: ephram@violet.berkeley.edu
Newsgroups: comp.lang.c
Subject: Re: TurboC
Message-ID: <4376@jade.BERKELEY.EDU>
Date: Thu, 16-Jul-87 20:49:50 EDT
Article-I.D.: jade.4376
Posted: Thu Jul 16 20:49:50 1987
Date-Received: Tue, 21-Jul-87 04:13:18 EDT
References: <8293@brl-adm.ARPA>
Sender: usenet@jade.BERKELEY.EDU
Reply-To: ephram@violet.berkeley.edu ()
Organization: University of California, Berkeley
Lines: 31

In article <8293@brl-adm.ARPA> oxy!bagpiper@csvax.caltech.EDU (Michael Paul Hunter) writes:
>People keep mentioning stuff about TurboC bugs and their fixes.  From
>what I gather, the DTM of the file(s) change but not the version number(1.0).
>We have a version of TurboC that we are thinking of using on a project.  If
>anybody could post (I think this is of general interest) the DTM's of each
>new mini-minor version, it would be a help.  At the least I would be interested
>in the DTM of the most current copy of TurboC that Borland is shipping.
>
>                                    Thanks
>
>Michael Hunter         UUCP  : ....{seismo, rutgers, ames}!cit-vax!oxy!bagpiper
>Box 241                ARPA  : oxy!bagpiper@csvax.caltech.edu
>Occidental College     BITNET: oxy!bagpiper@hamlet.bitnet
>Los Angeles, CA 90041  CSNET : oxy!bagpiper%csvax.caltech.edu@relay.cs.net

The date of the latest version that I have is 6-3-87 1:00a.  I got it from
the borland folk as an update because I couldn't apply the patches (I forgot
to rename my exe file to anything != exe so debug applied offsets to 
relocatable ...).  The original version was one of the earlier versions
I purchased it in the 1st few days from a company that drove down to borland
the day it was shipped and got a truckload.  I did a file compare with
the version I already had and found out that aside the 3 patches I have
division of constants, -G and structure push floating point patch) the
files compared exactly the same.

I really must say that the people at borland are willing to help and
have a satisfactory resolution alternitive to "You will have to wait for
version X.1.2.3.2.1.5".  
 

ephram@violet.berkeley.edu