Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!think.com!snorkelwacker.mit.edu!thunder.mcrcim.mcgill.edu!clyde.concordia.ca!altitude!matrox!uvm-gen!kira!nic!news.cs.brandeis.edu!news!phils
From: phils@chaos.cs.brandeis.edu (Phil Shapiro)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Bug with THINK C 4.0 scanf()?
Message-ID: <PHILS.91May2152425@chaos.cs.brandeis.edu>
Date: 2 May 91 19:24:25 GMT
References: <1991Apr30.081412.8116@beaver.cs.washington.edu>
	<1991May1.123600.3571@waikato.ac.nz>
Sender: usenet@news.cs.brandeis.edu
Distribution: na
Organization: Symantec Corp.
Lines: 27
In-Reply-To: johnc@waikato.ac.nz's message of 1 May 91 00:36:00 GMT

In article <1991May1.123600.3571@waikato.ac.nz> johnc@waikato.ac.nz writes:
   In article <1991Apr30.081412.8116@beaver.cs.washington.edu>, chou@cs.washington.edu (Pai Chou) writes:
   > I am having a problem with THINK C's scanf for doubles.
   > For example, if I scan in a double like 0.0258, I get back 0.258
   > -- it seems that the leading zeros are ignored.
   > 
   > Is anybody else having the same problem?  Does anyone
   > know a fix?  I am using version 4.0.  Is it fixed in
   > the upgrade?  Thanks
   > 
   > Pai Chou
   > chou@june.cs.washington.edu

   I'm having exactly the same problem and was searching this newsgroup for the
   answer!

The answer is: Get the 4.0.2 Think C update.  It fixes this bug in the
scanf() code, as well as minor bugs in the TCL and in the compiler
itself.  You can ftp this patch from sumex.stanford.edu (36.44.0.6),
under the path /info-mac/lang/think-c-402-update.hqx (or possibly
.sit.hqx, I forget).  It's a binhex'd stuffit archive.

	-phil
--
   Phil Shapiro                           Technical Support Analyst
   Language Products Group                     Symantec Corporation
		Internet: phils@chaos.cs.brandeis.edu