Color Class has a bug
andreas.raab at gmx.de
Thu Nov 9 18:23:22 UTC 2006
ncellier at ifrance.com wrote:
> This kind of weirdness motivated the design of SqueakNumberParser in 3.9 (hey, do not blame me, error pre-existed as a change in Integer>>readFrom:base: ).
> SqueakNumberParser is able to raise an error, but default behavior is rather to answer 0 like previous 3.9 implementation...
> Shouldn't this change in next version 3.10 or 4.0 ?
What I'd be more interested in is why the error-raising condition in 3.8
(which is clearly correct!) got removed in 3.9. Unfortunately (sigh)
there is no method history in 3.9 (double-sigh) and neither change set
information to find out how this was introduced (triple-sigh).
More information about the Squeak-dev