June 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Is the merge tool broken in 30126?

by StÃ©phane Ducasse

apparently it is broken when I enable FT2 So I removed it and it works. Stef On Jun 25, 2013, at 10:39 AM, StÃ©phane Ducasse <Stephane.Ducasse(a)inria.fr> wrote: > Because I cannot merge my fix 10735 to understand the conflicts ;( the merge tools does not show up. > I will see how I can recover my work because I spent some hours on it. > > Stef

June 25, 2013

Re: [Pharo-dev] Object >> #is:

by Igor Stasenko

On 25 June 2013 10:51, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On Jun 25, 2013, at 10:47 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 25 June 2013 10:28, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> On Jun 24, 2013, at 6:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> >>>> >>>> On 2013-06-24, at 18:55, StÃ©phane Ducasse <stephane.ducasse(a)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? > Object selectors select: [ :each | each beginsWith: 'is' ] #(#isThisEverCalled #isMorphicEvent #isCollection #isSpecLayout #isCodeCompletionAllowed #isComplex #isTransferable #isLiteral #isKindOf: #isInterval #isMorphicModel #isStream #isMorph #isPoint #isTrait #isCompiledMethod #isCharacter #isMessageSend #isText #isBlock #isRectangle #isContext #isBehavior #isArray #isVariableBinding #isColorForm #isSymbol #isDictionary #isHeap #isNumber #isSystemWindow #isThisEverCalled: #isString #isNotNil #isRingObject #isMethodProperties #isInteger #isFraction #isColor #is: #isClosure #isFloat #isMemberOf: #isForm #isSelfEvaluating) you welcome :) >> >>> 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. >> > > -- Best regards, Igor Stasenko.

June 25, 2013

Re: [Pharo-dev] Object >> #is:

by Esteban Lorenzano

On Jun 25, 2013, at 10:47 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 25 June 2013 10:28, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> On Jun 24, 2013, at 6:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> >>> On 2013-06-24, at 18:55, StÃ©phane Ducasse <stephane.ducasse(a)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. >

June 25, 2013

Re: [Pharo-dev] Object >> #is:

by Igor Stasenko

On 25 June 2013 10:28, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On Jun 24, 2013, at 6:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> >> On 2013-06-24, at 18:55, StÃ©phane Ducasse <stephane.ducasse(a)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 :) > 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.

June 25, 2013

Is the merge tool broken in 30126?

by StÃ©phane Ducasse

Because I cannot merge my fix 10735 to understand the conflicts ;( the merge tools does not show up. I will see how I can recover my work because I spent some hours on it. Stef

June 25, 2013

Re: [Pharo-dev] Object >> #is:

by Esteban Lorenzano

On Jun 24, 2013, at 6:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-06-24, at 18:55, StÃ©phane Ducasse <stephane.ducasse(a)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 :) 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...

June 25, 2013

pullup instance variable is wrong

by StÃ©phane Ducasse

Hi when you do a pull up one class, the system pull the instance variable on the originating class. When you try on the superclass you cannot access the iv of the subclasses. So we cannot do a pull up iv at all. Stef

June 25, 2013

Please review 10950 10983

by Gisela Decuzzi

Subj. to see if we can integrate them and keep working on that.

June 25, 2013

Re: [Pharo-dev] Object >> #is:

by StÃ©phane Ducasse

On Jun 24, 2013, at 6:59 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-06-24, at 18:55, StÃ©phane Ducasse <stephane.ducasse(a)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. Not only :) > 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â¦ I agree

June 24, 2013

Re: [Pharo-dev] Object >> #is:

by Camillo Bruni

On 2013-06-24, at 18:55, StÃ©phane Ducasse <stephane.ducasse(a)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. 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...

June 24, 2013