From -308010925179776624
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10f5bc,6f6e97a6fdbbf44c
X-Google-Attributes: gid10f5bc,public
X-Google-Thread: 1149ec,6f6e97a6fdbbf44c
X-Google-Attributes: gid1149ec,public
X-Google-Thread: 1014db,6f6e97a6fdbbf44c
X-Google-Attributes: gid1014db,public
X-Google-Thread: 102b75,6f6e97a6fdbbf44c
X-Google-Attributes: gid102b75,public
X-Google-Thread: 109fba,6f6e97a6fdbbf44c
X-Google-Attributes: gid109fba,public
X-Google-Thread: 110292,6f6e97a6fdbbf44c
X-Google-Attributes: gid110292,public
X-Google-Thread: f78e5,6f6e97a6fdbbf44c
X-Google-Attributes: gidf78e5,public
From: xzz0529@honker.rchland.ibm.com (Jonathan Allan)
Subject: Re: And you thought that the Pentium bug was bad!  (Get a load of this!)
Date: 1995/06/22
Message-ID: <3sbm5j$vuq@locutus.rchland.ibm.com>#1/1
X-Deja-AN: 104873934
distribution: world
references: <3s2las$1br@hustle.rahul.net> <3s46bi$3qe@devel.dvstsol.demon.co.uk>
organization: IBM Rochester MN
reply-to: kpa@mill2.millcomm.com
newsgroups: comp.std.c,comp.std.c++,comp.lang.c,comp.lang.c++,comp.sys.intel,comp.arch,comp.software.testing

In article <3s46bi$3qe@devel.dvstsol.demon.co.uk>, nick@dvstsol.demon.co.uk (Nick Gorham) writes:
[slice] 
|> Perhaps I am missing the point, but whats the above bit of silly code
|> to do with floating point errors. The simple way to fix this "compilor bug"
|> is not to write code like this ;-). Perhaps someone will tell otherwise.

Ah!  The dreaded "Don't *DO* that!" answer.

Jonathan (And why not?) Allan
-- 
*  Nobody except me has any stake in this opinion, and *
*  if I'm playing Devils Advocate, even *I* don't.     *
*  Email to kpa@mill2.millcomm.com won't bounce.       *
* It won't be answered either until I get my hardware fixed. *