On Wed, 09 Feb 2005 11:48:30 -0800, Debian Bug Tracking System wrote > This is an automatic notification regarding your Bug report > #294386: Arithetical bug in perl?, > which was filed against the perl package. > > It has been closed by one of the developers, namely > Florian Weimer <[EMAIL PROTECTED]>. > > Their explanation is attached below. If this explanation is > unsatisfactory and you have not received a better one in a separate > message then please contact the developer, by replying to this email. > > Debian bug tracking system administrator > (administrator, Debian Bugs database) > > Received: (at 294386-done) by bugs.debian.org; 9 Feb 2005 19:39:42 +0000 > >From [EMAIL PROTECTED] Wed Feb 09 11:39:42 2005 > Return-path: <[EMAIL PROTECTED]> > Received: from mail.enyo.de [212.9.189.167] > by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) > id 1Cyxgc-0005Al-00; Wed, 09 Feb 2005 11:39:42 -0800 > Received: from deneb.enyo.de ([212.9.189.171]) > > by albireo.enyo.de with esmtp id 1CyxgY-0003M7-3J; Wed, 09 Feb 2005 > 20:39:38 +0100 Received: from fw by deneb.enyo.de with local (Exim > 4.43) > id 1CyxgW-0007Nn-3e; Wed, 09 Feb 2005 20:39:36 +0100 From: Florian > Weimer <[EMAIL PROTECTED]> To: "Rafal Ramocki" <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] Subject: Re: Bug#294386: Arithetical > bug in perl? References: <[EMAIL PROTECTED]> > Date: Wed, 09 Feb 2005 20:39:36 +0100 In-Reply-To: > <[EMAIL PROTECTED]> (Rafal Ramocki's message of > "Wed, 9 Feb 2005 17:53:16 +0330") Message-ID: <[EMAIL PROTECTED]> > MIME-Version: 1.0 > Content-Type: text/plain; charset=us-ascii > Delivered-To: [EMAIL PROTECTED] > X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 > (1.212-2003-09-23-exp) on spohr.debian.org > X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00, > HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 > X-Spam-Level: > > * Rafal Ramocki: > > > I was writing a small script, but happened something wired. > > This is not a bug, this is how floating point arithmetic works. In > binary floating point arithmetic, 0.01 has no exact representation > (like one third in decimal floating point). The errors pile up, and > after a few iterations of your loop, they become apparent.
OK. I Understand. I'm sorry for false alarm, and i'm sorry for wasting Your time. :( -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
