Re: [Pharo-dev] Parsing float difference between 2.0 and 3.0, was it on purpose?

2015-02-09 Thread stepharo
Hi nicolas. No it's not strange. 2 different parsers respond to 2 different syntax and expectations. To me it's quite clear: - The SmalltalkNumberParser was there to parse a Smalltalk syntax (badly named SqNumberParser in the ages...) It should do this thru Number readSmalltalkSyntaxFrom:

Re: [Pharo-dev] Parsing float difference between 2.0 and 3.0, was it on purpose?

2015-02-09 Thread Mariano Martinez Peck
On Fri, Feb 6, 2015 at 7:45 AM, Yuriy Tymchuk 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 random

Re: [Pharo-dev] Parsing float difference between 2.0 and 3.0, was it on purpose?

2015-02-06 Thread Nicolas Cellier
2015-02-06 16:18 GMT+01:00 Marcus Denker : > > > On 06 Feb 2015, at 11:45, Yuriy Tymchuk 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 functionali

Re: [Pharo-dev] Parsing float difference between 2.0 and 3.0, was it on purpose?

2015-02-06 Thread Marcus Denker
> On 06 Feb 2015, at 11:45, Yuriy Tymchuk 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 > rand

Re: [Pharo-dev] Parsing float difference between 2.0 and 3.0, was it on purpose?

2015-02-06 Thread Yuriy Tymchuk
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 dec

Re: [Pharo-dev] Parsing float difference between 2.0 and 3.0, was it on purpose?

2015-02-06 Thread Marcus Denker
> On 06 Feb 2015, at 09:02, stepharo wrote: > > > Le 5/2/15 10:40, Sven Van Caekenberghe a écrit : >>> On 05 Feb 2015, at 10:36, Ben Coman wrote: >>> >>> I personally would prefer to be able to use exponents. No sure what the >>> big picture is. >>> cheers -ben >> Of course exponents are st

Re: [Pharo-dev] Parsing float difference between 2.0 and 3.0, was it on purpose?

2015-02-06 Thread stepharo
Le 5/2/15 10:40, Sven Van Caekenberghe a écrit : On 05 Feb 2015, at 10:36, Ben Coman 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 expone

Re: [Pharo-dev] Parsing float difference between 2.0 and 3.0, was it on purpose?

2015-02-05 Thread Sven Van Caekenberghe
> On 05 Feb 2015, at 10:36, Ben Coman 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 tra

Re: [Pharo-dev] Parsing float difference between 2.0 and 3.0, was it on purpose?

2015-02-05 Thread Ben Coman
I personally would prefer to be able to use exponents. No sure what the big picture is. cheers -ben On Thu, Feb 5, 2015 at 12:27 AM, Mariano Martinez Peck < marianop...@gmail.com> wrote: > Hi guys, > > In Pharo 2.0, the expression "Number readFrom: '2.58500098e+04' " > would answer 25850

[Pharo-dev] Parsing float difference between 2.0 and 3.0, was it on purpose?

2015-02-04 Thread Mariano Martinez Peck
Hi guys, In Pharo 2.0, the expression "Number readFrom: '2.58500098e+04' " would answer 25850.01 , but in Pharo 3.0 it answers: 2.58500097 which is a kind of WTF to me. Checking the differences it seems in Pharo 2.0 ExtendedNumberParser (used from Number >> readFrom: ) implement