So in talking to a friend of mine from Indiahttp://en.wikipedia.org/wiki/India, they have a numeral system using *lakhs http://en.wikipedia.org/wiki/Lakh* (*lacs*) (1,00,000 equal to 100 000) and *croreshttp://en.wikipedia.org/wiki/Crore * (1,00,00,000 equal to 10 000 000). Then of course when you get to big numbers they express things in crores. So you can see 1,00,000 crores (or 1,00,000,00,00,000).
Bottom line. I don't think the need for this change is that great and too many issues. I'll dip into smalltalk when needed.
Thanks, Stephen
On Mon, Jul 9, 2012 at 10:03 AM, Steve Thomas sthomas1@gosargon.com wrote:
On Mon, Jul 9, 2012 at 5:32 AM, Bert Freudenberg bert@freudenbergs.dewrote:
On 2012-07-08, at 22:01, Steve Thomas wrote:
Well second coolest "when it works" :)
So I was able to change 1000 to '1,000' but when I used the numeric
value of '1,000' I get 1 instead of 1000 (note already put an enhancement request in tracker).
So how can I remove translate '1,000' to 1000? Tried method finder, but
no luck using "'1,000'. 1000".
Well, the method finder works only if a single method does what you need, and there is no such method. One example that is helpful would be
'1,000' . ',' . '1000'or the less obvious
'1,000' . $, . '1000'(which uses Smalltalk's notation for characters)
Cool thanks.
I can think of a couple ways of doing this (ex: iterate through the
characters and remove commas) But there really should be an easier more Etoys friendly way.
Also for internationalization I noticed that the decimal mark is always
a period (even when using German, perhaps they have finally realized we have a better system, dividing by 10 is too easy and requires no hard fun ;)
I don't get the joke why you think any of the notations is inherently "better".
But maybe we can agree that mixing commas and dots is not ideal. Switching the notation based on locale is no solution either. Projects that use numerical strings would become dependent on the locale.
Agreed.
The best way I can think of is following the ISO recommendation of using spaces for digit grouping. This could be a relatively simple change, and would be unambiguous internationally.
I like it, need to think about it some more though. For existing projects displaying using spaces for digit grouping could throw off layout on some existing projects.
Stephen