How about making it an a type instead; Money class perhaps? Calculating it or displaying it would then be the responsibility of the type. You can make it bahave as a double or a decimal by using operator overloading the necessary operators and when you want to print it out, call ToString instead. If you are really paranoid about space, you can make a boatload of classes implementing the IMoney interface and let the Money class use the most appropriate representation as required. If the money is a whole number, it will use the IntMoney. If certain calculations resulted in the money having cents, then use decimal. If you are working on a freak calculation running into millions of digits of money (wow), then revert to a string representation or a multi-byte implementation instead. This all happens inside the Money class. Users of money can use the familiar interface using mathematical operators and such. Of course, it sounds complicated and too much work. However, in a financial application where Money is the center of everything, don't you think it is all worth it?

YAGNI :) the only reason I'll think of doing such a Money type is to accommodate multiple currencies

Of course I am not suggesting that he implement a full blown multicurrency money class right away :-). YAGNI would apply right away because I am implementing something that I "think" I would need in the future. However, what I am trying to say is use the Money class to delay the design decision until such a time that you have more information about the problem. Instead of deciding *now* whether to use double or decimal, let the application be built around a Money class and then let Money internally use double. If you found out in the future that you will need to use decimal instead, then the changes that you would need to make is isolated in the Money class. A single currency money class is simple to make and only needs to support limited functionality (addition or subtraction? I've never heard of someone finding the sin or cosine of Monies, yet). :-).

galing talaga ni uncle jop...hawig kay uncle bob. So what you're saying is "delaying design decision until the last responsible moment is another way of saying YAGNI"? While there seems to be some overhead in coming up with a new type, I would agree with Jop that this will save you grief later on...unless this part of your code is a one-off or tangential to the application.

Hey, someone here agrees with me. That's odd? :D

Amoxicillin. Safety of amoxicillin and greyhounds. Amoxicillin alternative. Dosing of amoxicillin for sinus infection. Amoxicillin and strep b. Bleeding and amoxicillin.

eAPQHt0 | chubby mature webcams granny