On Fri, Feb 6, 2015 at 7:45 AM, Yuriy Tymchuk <[email protected]> wrote:
> We have merged the parsers into one, because we had 3 parsers that didn’t > have any dedicated use-cases, juts were developed historical as at some > point someone needed a bit more functionality, and then different parsers > were used randomly on the system. As for the expression - yes we have to > decide about it. If it’s only about being able to use exponent in float > literals, one can use: “Number readFrom: '2.5850009999999998e04’”. If it’s > about being similar to the other languages, we can also decide does it make > sense to have a +2 literal. > > Yes, I would allow that by default. This will ease serialization between Pharo and GemStone for example (which uses +). So..... what I would do is to simply change to NumberParser >> allowPlusSignInExponent ^ true I opened: https://pharo.fogbugz.com/f/cases/14896/By-default-float-parsing-does-not-allow-plus-symbol-in-exponential Cheers, Uko > > > On 06 Feb 2015, at 09:04, Marcus Denker <[email protected]> wrote: > > > > > >> On 06 Feb 2015, at 09:02, stepharo <[email protected]> wrote: > >> > >> > >> Le 5/2/15 10:40, Sven Van Caekenberghe a écrit : > >>>> On 05 Feb 2015, at 10:36, Ben Coman <[email protected]> wrote: > >>>> > >>>> I personally would prefer to be able to use exponents. No sure what > the big picture is. > >>>> cheers -ben > >>> Of course exponents are still supported ;-) > >>> > >>> The discussion is about the + sign for positive exponents. I am not > sure, but I think that traditional Smalltalk did not support this, but it > was added to support common practice in other languages. Now it is > apparently gone again, probably not on purpose. > >> > >> I do not know I think that marcus removed it to avoid to have two > parsers in the image. > >> > > > > Maybe this was a mistake… > > > > Marcus > > > -- Mariano http://marianopeck.wordpress.com
