Re: Unexpected behavior of NSNumberFormatter
Re: Unexpected behavior of NSNumberFormatter
- Subject: Re: Unexpected behavior of NSNumberFormatter
- From: Thomas Lachand-Robert <email@hidden>
- Date: Sun, 30 Dec 2001 17:24:42 +0100
Le dimanche 30 dicembre 2001, ` 01:58 , Nick M|ller a icrit :
Just for the one who will fix it, not for complaining:
- Also the rounding seems to be buggy. Rounding-behavior claims to not
limit the number of digits after the decimal point, but it does (to 2
digits).
- NSDecimalNumberHandler does not respond to NSCoding. If you replace
the rounding behavior by your own,
(NSNumberFormatter:setRoundingBehavior) and try to archive the
NSNumberFormatter, you will miss NSCoding.
- I'm also missing some set-functions in the NSDecimalNumberHandler. The
NMSDecimalNumberBehavior-protocol only allows reading.
Just my 2 cents, but I would like to remind you one of the best features
of Obj-C: you can always add new methods to existing classes, or even
change the existing ones. In your example, if some class doesn't implement
the NSCoding protocol, you can add it yourself if you are able to
construct the class objects with the usual init... methods (for
unarchiving), and if you can acceed the contained information (for
archiving).
This helps to wait until Apple corrects the bug... ;-)
Thomas Lachand-Robert
********************** email@hidden
<< Et le chemin est long du projet ` la chose. >> Molihre, Tartuffe.