Path: utzoo!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!pasteur!ames!oliveb!apple!bbn!mit-eddie!uw-beaver!tektronix!tekcrl!tekgvs!keithe
From: keithe@tekgvs.LABS.TEK.COM (Keith Ericson)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Turbo C vs. Pascal
Message-ID: <4740@tekgvs.LABS.TEK.COM>
Date: 9 Mar 89 06:11:13 GMT
References: <46500039@uxf.cso.uiuc.edu> <52903@yale-celray.yale.UUCP>
Reply-To: keithe@tekgvs.LABS.TEK.COM (Keith Ericson)
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 19

In article <52903@yale-celray.yale.UUCP> spolsky-joel@CS.YALE.EDU (Joel Spolsky) writes:
<In article <46500039@uxf.cso.uiuc.edu> mwh1629@uxf.cso.uiuc.edu writes:
<| 
<| Lastly, what's the deal with version numbers?  I think I
<| was told that, for example, Version 2.34 means that 4 is a bug fix, 3 is a
<| minor improvement and 2 is a major change.  Is this correct?
<
<No hard and fast rules. The rule I like is that changing the integer
<means a major rewrite, the .1 reflects new features, the .01 is
<anything that is usually transparent to the user (bug fixes or
<speedups). 
<

Except for Microsoft: X.YZ where Y=0 means it's a Beta Release. Y >=2
means it's maybe OK, but you're safest to hold out for Y >=3. Z <> 0
means it's a minor tweak.  Also, there are extensions (e.g., MS-DOS 3.30A)
that No one understands...

kEITH (only joking) (maybe) eRICSON