On Jun 25, 2013, at 10:47 AM, Igor Stasenko <siguctua@gmail.com> wrote:
On 25 June 2013 10:28, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On Jun 24, 2013, at 6:59 PM, Camillo Bruni <camillobruni@gmail.com> wrote:
On 2013-06-24, at 18:55, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
the isBlah is not optimal now it is just there and we cannot rewrite everything. I still think that is: is a nice way to kill some of the isPlague in Object.
I still don't see what you solve, and the idea to use symbols for #is: is also wrong, for me that's going back to string-based programming.
well, that's basically my argument agains #is: IMO is also an important performance issue in many cases, because is replacing a simple send with a string comparison and that can provoke slowdowns in some places (no idea where, this is just theoretical :)... Of course, as "pharo designers" we should be careful on not overpopulate Object with isBlah methods... but sometimes they are needed :)
yes, but please, do that, after you remove rest of isXXX methods in Object :)
which rest?
TL;DR: I agree with Camillo :)
anyway, this topic has been discussed with enough hot air so far and no progress, which means it is absolutely not important. there are more urgent things to done...
-- Best regards, Igor Stasenko.