A FogBugz case was edited by Marcus Denker.
Case ID: 10016
Title: Pharo and scaled decimals
Status: Resolved (Fix Review Needed)
Category: Bug
Project: Number
Area: Misc
Priority: 4 - Would be nice
Milestone: Pharo3.0: 30/03/2014
Assigned To: Marcus Denker
URL:
https://pharo.fogbugz.com/default.asp?10016Changes:
Priority changed from '6 - On Hold' to '4 - Would be nice'.
so the strange thing is that this is *explicitly* implemented in SqNumberParser to not allow 2.0s
- do not allow single s without following digits as ScaledDecimal
It is not explained why this is a good idea.
In general, we need to merge the whole NumberParser hierarchy into one class, i don't understand why we have three classes now.
You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (
https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&command=view&ixBug=10016) from this case.
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker