Originally posted by Wyrm
I wonder if there is a problem in OSX?
-Wyrm
Originally posted by steadyeddie
Think yourself lucky... anyone remember when the Windows 95 calculator used to do this:
1.01 - 1 = 0.0
Pretty big rounding error if you ask me!
![]()
Originally posted by Powerbook G5
I remember the original Pentium processor had a big error with its math co-processor which led to all kinds of quirks when the first Pentiums came out with Windows 95.
As stated, this is a problem with floating point arithmetic. Any calculator program I have made in C++ I have always put error checks in, which isn't that difficult. Also, I believe the reason that you notice in on windowsupdate with Windows under VPC is because of the floating point arithmetic while converting from x86 to PPC. I don't know much about the PPC architecture (new to Macs), but I am also wondering why this seems to be more prevalent in the Mac calculator programs. Are the programmers just lazy in putting in checks for this, or is this an inherent inadequacy of the PPC architecture?Originally posted by crash_harddrive
I just got off the phone with Mac tech support, it seems this is a more common error than I assumed at first. I have a G5 which can't do basic math (and this is in the calculator display, not the tape) but the tech I talked to repeated the problem on a G3 iMac. Seems like a shame that I spent about 4 grand on a computer and now I'll have to spend another $30 on a desktop calculator so I can balance my checkbook. The tech referred me to an article that basically reads "Sorry about your luck", it seems that Apple doesn't find the calculator important enough to fix. BTW, I downloaded two freeware calc apps and both had the same problem so this is a Mac problem in general, not the application. I am at a loss as to why the beast of Redmond can make a working calc program but Apple is clueless. It seems to me that if Apple can't make a working calculator they should leave the app out entirely.
Originally posted by Vector
I tried doing the same exact calculations and it did them fine. I am using version 3.1.
Originally posted by abhishekit
well that happens because the precision is set to 12 digits..just goto view-precision and set it to 2..viola it works again...i dont get how this can be considered a bug?!!
Originally posted by NuPowerbook
I take it you have never programmed a something that did floating point arithmetic. It's a bug because that's not what the answer is. Do it in your head, on paper, with a handheld calculator, and you will see it is wrong. When doing floating point arithmetic, a lot of casting goes on, so there are inevitable mistakes. Most programmers will take the time to put something in to prevent or catch something like this from happening. Setting the precision to two will only cover it up, not fix it.
Originally posted by abhishekit
yah..never...but anyways i think the guy who started the thread was looking to use the cal and not invent it...
Originally posted by abhishekit
well that happens because the precision is set to 12 digits..just goto view-precision and set it to 2..viola it works again...i dont get how this can be considered a bug?!!