Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!asuvax!noao!ncar!gatech!udel!rochester!cornell!vax5.cit.cornell.edu!u2zj
From: u2zj@vax5.cit.cornell.edu (Stanton Loh)
Newsgroups: comp.sys.mac.programmer
Subject: Re: Think C scanf() bug?
Message-ID: <1991Mar17.223828.3441@vax5.cit.cornell.edu>
Date: 18 Mar 91 02:38:28 GMT
References: <1991Mar17.230413.1917@leland.Stanford.EDU>
Followup-To: noa@leland.stanford.edu,comp.sys.mac.programmer
Distribution: comp
Organization: CIT, Cornell University
Lines: 20

In article <1991Mar17.230413.1917@leland.Stanford.EDU>,
noa@leland.Stanford.EDU (Noa More) writes:
> Sender:Noa Rensing
>
> I recently bought a Mac IIsi (with a math co-processor) and got
> Think C 4.00 for it at the educational price. Previously I have
> used Microsoft QuickC and C6.0 and TurboC on DOS machines and
> several different Unix C compilers. I was extremely disappointed
> with the programming enviroment offered by Think C, and I was
> wondering if anyone had any suggestions:
>
> 1. (The most serious) If I use scanf() with floats, the numbers I
> get from the input are completely unrelated to the input, as in:
>

Rebuild the ANSI library, commenting out the #define _NOFLOATING_
statement in ansi_config.h.

-Stanton Loh
u2zj@vax5.cit.cornell.edu.