On Fri, 23 Jun 2000, Bill Gribble wrote:
> 7. Abstraction. Since we have made at least one fundamental mistake
> in specifying the original representation of monetary values in
> gnucash, we have to assume that we may make others. We are going
> to have to do significant surgery on gnucash to remove instances
> of double math using built-in operators;
This is the key thing. The program should never care how the money is stored.
It simply tells the money handler to perform the desired operation.
> 8. Fixed storage size. Considering that the gnucash engine may at
> some time have a database backend, it's important to have a
> numeric format that has a fixed storage size and (optimally) can
> be directly operated on by SQL operators.
Actually, this is not important if you have done #7 correctly.
We can have multiple compilations of gnucash which have totally different
representations. One possibility would be to use the "native" representation
of whatever backend storage system you are using.
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
