may be you are right.
I do not know
so at least we should check all the users in the system
On Oct 27, 2009, at 3:13 PM, Niko Schwarz wrote:
> Well, by doing that you will confuse users that only relied on the
> consensual functionality of asNumber.
>
> It's difficult both ways, and because of tha
Well, by doing that you will confuse users that only relied on the
consensual functionality of asNumber.
It's difficult both ways, and because of that, I'd suggest going the
lazy way and not helping the users other than by adding a comment to
#asNumber which explains the evolution of the message
Not really
we could do the following
- check all the users of asNumber and let them as asNUmber or
squeezeOutNumber
- then put a deprecation during the alpha phase that state that they
should pay attention
- when we are in rc 1.1 we remove the deprecation
- crea
Well, what do you propose? Deprecating asNumber calls altogether?
Cheers,
Niko
On Sat, Oct 24, 2009 at 10:32 AM, Stéphane Ducasse
wrote:
> Yes a good deprecation is needed.
>
> Stef
> On Oct 24, 2009, at 11:13 AM, Adrian Lienhard wrote:
>
>> Sounds ok. At the same time as integrating the change
Yes a good deprecation is needed.
Stef
On Oct 24, 2009, at 11:13 AM, Adrian Lienhard wrote:
> Sounds ok. At the same time as integrating the change, all senders of
> asNumber in the image need to be checked and adapted to the new
> semantics if necessary. IIRC MC was not properly working after th
Sounds ok. At the same time as integrating the change, all senders of
asNumber in the image need to be checked and adapted to the new
semantics if necessary. IIRC MC was not properly working after the
change. Also, users and maintainers of external packages should be
made aware of the chang
Thanks niko
So does everybody agree with
asNumber raising an error
and
squeezeOutNumber
I like the proposal.
Stef
On Oct 24, 2009, at 10:30 AM, Niko Schwarz wrote:
> Hi all, I made a follow-up patch like discussed on the workshop. Now
> porting becomes as easy as
Hi all, I made a follow-up patch like discussed on the workshop. Now
porting becomes as easy as changing "asNumber" to "squeezeOutNumber".
Name: SLICE-issue-1258-squeezeOutNumber-NikoSchwarz.2
This slice adds squeezeNumberOutOfString: to Number, as discussed in
the Pharo workshop. On the way, it
10492 (this is the stream of the branch 1.0rc1)
-
- Issue 1320: [squeak trunk] Sort the conflicts. This is required when
merging a distant version, like Pharo for example...
- Issue 1338: HostWindowTests>>testOne is failing in Windows
- Issue 1345: Revert Number class>>readFrom: (was i
