Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!csus.edu!ucdavis!iris!lim
From: lim@iris.ucdavis.edu (Lloyd Lim)
Newsgroups: comp.sys.mac.programmer
Subject: THINK C bug
Message-ID: <8396@ucdavis.ucdavis.edu>
Date: 19 Feb 91 03:56:29 GMT
Sender: usenet@ucdavis.ucdavis.edu
Reply-To: lim@iris.ucdavis.edu (Lloyd Lim)
Organization: U.C. Davis - Department of Electrical Engineering and Computer Science
Lines: 19

I think I've ran across another pair of bugs in THINK C 4.0.2.  The following
code works OK with 68881 code generation off but doesn't when it's on.

double x;
unsigned long u;

x = ULONG_MAX;

u = 3.0e+9;

The first statement works normally but assigns a -1.0 when the 68881 option
is on.  The second statement also works normally but assigns 0x7FFFFFFF when
the 68881 is on.  It seems like THINK C forgets that unsigned longs exist.
Yes, you can work around it but it's annoying.

+++
Lloyd Lim     Internet: lim@iris.eecs.ucdavis.edu
              Compuserve: 72647,660
              US Mail: 215 Lysle Leach Hall, U.C. Davis, Davis, CA 95616