Purely for display. I'm doing a very basic accounting app that does not need full accuracy, but saying that the client should pay (X/Y) amount of cash .. that will be a problem :) In the end, I might as well keep fractions for the model itself, and just add asFloat on the view wherever required. On Sat, Jul 31, 2010 at 10:41 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
That's the way I'm doing it now, but it's redundant to put asFloat at the end of each division. There *should* be a more elegant way, at least I hope so :)
why? I do not like to manipulate float when I can have exact math operations. So I put asFloat exactly when I know I want to leave the math world to end up in the computer science world.
Why do you need float and not fraction? You crunch matrix resolution with large numbers?
Stef
_______________________________________________ Pharo-users mailing list Pharo-users@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users