[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Open Bugs in 3.2
From:       Rüdiger_Knörig <Ruediger.Knoerig () gmx ! net>
Date:       2004-01-13 13:01:02
Message-ID: 200401131401.03090.Ruediger.Knoerig () gmx ! net
[Download RAW message or body]

IMHO the key is the seperation into a "simple" and a "scientific" mode most 
"virtual" calculators provide. It seems that in "simple" mode  fixed-point 
arithmetic or even better, BCD-coded arithmetics would be the best while in
scientific mode floating point numbers would be the best representation.
At least the x86 architecture has dedicated processor ops to handle such 
numbers (they've been or are (?) very important for financial calculations 
since you can encode decimals exactly).

One solution could be the seperation of the calculation engine from the 
"frontend". The calculation engine could be written datatype-independend 
using templates, and the selection could be done by using a reference to an 
instanciation from the "correct" data type.

Or we could simply use "bc" encapsulated in a QProcess.
 
-- 
Rüdiger Knörig
Institut für Fernmeldetechnik der TU Berlin
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]