Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-spam!ames!sdcsvax!ucsdhub!hp-sdd!hplabs!hpcea!hpsrla!hpsrlc!darrylo
From: darrylo@hpsrlc.UUCP
Newsgroups: comp.sys.ibm.pc
Subject: Re: 2 bugs in Turbo C
Message-ID: <3320022@hpsrlc.HP.COM>
Date: Tue, 16-Jun-87 11:30:50 EDT
Article-I.D.: hpsrlc.3320022
Posted: Tue Jun 16 11:30:50 1987
Date-Received: Fri, 19-Jun-87 05:28:18 EDT
References: <2879@zen.berkeley.edu>
Organization: Network Measurements Div - Santa Rosa, CA
Lines: 49

In comp.sys.ibm.pc, morearty@cory.Berkeley.EDU (Mike Morearty) writes:

> I have encountered two bugs in Turbo C that are worth mentioning:
> 
> (1) strstr() has problems.  One problem was mentioned in a previous

     Turbo C has a number of bugs, most of which get fixed soon after they
are found.  Borland seems to be fixing bugs and shipping the fixed versions
of the compilers to new customers (they don't seem to change the revision
number, though).  For example, one early version of the (shipped) compiler had
problems with dividing floating-point constants (4.0 / 2.0 would give 0.5 or
somesuch).  By the time I bought my copy, the compiler didn't have the bug
(it was still called version 1.0, however -- fortunately, the timestamp
does change).  I get the impression that the longer one waits, the less
bugs the compiler will have (not that Turbo C is buggy).

     There are other bugs in Turbo C, but Borland has issued patches for
most of them.  By patches, I mean actual instructions like "take out debug
and change the value at AAAA:XXXX from YY to ZZ".  Among the bugs fixed are:

     1. "Out of memory" error using the command-line version of the
	compiler with the "-G" option (optimize for speed).

     2. Problems with passing a structure containing floats to a function.

     3. The strstr() bug mentioned.  This was fixed by someone (not
	Borland?) simply rewriting the routine.

     4. Problems with dividing floating-point constants.

Even with the bugs it has (the ones above don't bother me as patches have
been issued), I like Turbo C (the compile speed is WONDERFUL).  Having
warnings like "possibly incorrect assignment" in an "if" statement (should
be equality, not assignment) is really nice!

[...]
> 
> --
> Mike Morearty
> ARPA: morearty@cory.Berkeley.EDU	USENET: ucbvax!cory!morearty
> ----------

     -- Darryl Okahata
	hplabs!hpcea!hpsrla!darrylo
	CompuServe: 75206,3074

Disclaimer: the above is the author's personal opinion and is not the
opinion or policy of his employer or of the little green men that
have been following him all day.