If you're doing financial software, then you most certainly *do not* want to be using Number or any subclass thereof for your calculations. It's not accurate, nor is it meant to be, and you'll get weird edge-case errors that end up taking weeks to debug. Build a dedicated currency class that works with integer values, and build your toString() into that class if you're dead against CurrencyFormatter for whatever reason.
-Josh On Feb 11, 2008 6:52 PM, Paul Andrews <[EMAIL PROTECTED]> wrote: > ----- Original Message ----- > From: "okegbenle mayowa" <[EMAIL PROTECTED] <brainny2002%40yahoo.com>> > To: <[email protected] <flexcomponents%40yahoogroups.com>> > Sent: Monday, February 11, 2008 8:24 AM > Subject: Re: [flexcomponents] Re: Extending the Number Class > > > thanks all, > > @reflaxations, what u r suggesting is the composition > > technique i tried, the results are not impressive. > > What do you mean by unimpressive? > > Surely it's fairly simple to do what you need by composition? > > Paul > > -- "Good people will do good things, and bad people will do bad things. But for good people to do bad things—that takes religion." :: Josh 'G-Funk' McDonald :: 0437 221 380 :: [EMAIL PROTECTED]
