August 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] 'foo' asTime

by StÃ©phane Ducasse

Ok normally this is integrated now. On Aug 27, 2010, at 12:11 PM, Johan Brichau wrote: > err, yes it actually still is this one: http://code.google.com/p/pharo/issues/detail?id=2854 > :-) > > On 27 Aug 2010, at 10:16, StÃ©phane Ducasse wrote: > >> johan >> >> thanks >> Now get the reflex to create an issue else we get flooded of information. >> I will integrate them now. >> >> Stef >> >> On Aug 26, 2010, at 2:34 PM, Johan Brichau wrote: >> >>> >>> On 26 Aug 2010, at 04:47, Guillermo Polito wrote: >>> >>>> And now, because of fixing Integer>>readFrom:, 'foo' asTime throws an exception and we all are a bit happier :D. >>> >>> Indeed. thanks. >>> And just to make sure that we keep being happy, I added some unit tests to verify that in the KernelTests package ;-) >>> >>> Johan >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 27, 2010

Re: [Pharo-project] 'foo' asTime

by Johan Brichau

err, yes it actually still is this one: http://code.google.com/p/pharo/issues/detail?id=2854 :-) On 27 Aug 2010, at 10:16, StÃ©phane Ducasse wrote: > johan > > thanks > Now get the reflex to create an issue else we get flooded of information. > I will integrate them now. > > Stef > > On Aug 26, 2010, at 2:34 PM, Johan Brichau wrote: > >> >> On 26 Aug 2010, at 04:47, Guillermo Polito wrote: >> >>> And now, because of fixing Integer>>readFrom:, 'foo' asTime throws an exception and we all are a bit happier :D. >> >> Indeed. thanks. >> And just to make sure that we keep being happy, I added some unit tests to verify that in the KernelTests package ;-) >> >> Johan >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 27, 2010

Re: [Pharo-project] class API question

by StÃ©phane Ducasse

> I think it would be beneficial to adapt the protocol of the refactoring browser. > > It especially spells out all the names: > > #addInstanceVariable: > #allInstanceVariableNames > #instanceVariableNames > > Lukas I thought about it too but since we will add first class instances variables then I preferred to use named: for now and like that we can have both interfaces in the future for compatibility. Stef

Aug. 27, 2010

[Pharo-project] [update 1.2] #12115

by StÃ©phane Ducasse

12115 ----- - Issue 2825: [[true] whileTrue] fork cannot be interrupted. Thanks Henrik Johanssen. - Issue 2860: make Dictionary at:ifAbsent use ifNil:ifNotNil. Thanks Marcus Denker - Issue 2570: Removed implicit conversion of DateAndTime equality-testing argument. Thanks Chris Mueller. We will have to address the isKindOf in DateAndTime>>= - Issue 2873: adding hasClassVarNamed: hasInstVarNamed: and cleaned the API. I feel better - Stephane Ducasse Stef

Aug. 27, 2010

Re: [Pharo-project] class API question

by Jorge Ressia

Yep, It would be much better to sell out the names. On Fri, Aug 27, 2010 at 11:53 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > I think it would be beneficial to adapt the protocol of the refactoring browser. > > It especially spells out all the names: > > Â Â #addInstanceVariable: > Â Â #allInstanceVariableNames > Â Â #instanceVariableNames > > Lukas > > On 27 August 2010 11:50, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> done :) >> I could not let that like that. >> >> Stef >> >> On Aug 27, 2010, at 11:11 AM, Marcus Denker wrote: >> >>> >>> On Aug 27, 2010, at 11:02 AM, StÃ©phane Ducasse wrote: >>> >>>> We are not consistent: >>>> >>>> Â Â Â do we want >>>> Â Â Â Â Â Â Â renameInstVar:to: >>>> Â Â Â or >>>> Â Â Â Â Â Â Â removeInstVarName: >>>> Â Â Â Â Â Â Â Â Â Â Â I prefer that. >>>> >>>> We have addInstVarName: >>>> Â Â Â -> should be addInstVarNamed: from my taste >>>> >>>> >>>> Now we want to have first class instance variable in the near future so I would like to have >>>> >>>> Â Â Â addInstVar: aVariable >>>> Â Â Â addInstVarNamed: aString >>>> >>>> What do you think? >>>> >>> >>> Yes! >>> >>> >>> -- >>> Marcus Denker Â -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Jorge Ressia www.jorgeressia.com

Aug. 27, 2010

Re: [Pharo-project] class API question

by Lukas Renggli

I think it would be beneficial to adapt the protocol of the refactoring browser. It especially spells out all the names: #addInstanceVariable: #allInstanceVariableNames #instanceVariableNames Lukas On 27 August 2010 11:50, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > done :) > I could not let that like that. > > Stef > > On Aug 27, 2010, at 11:11 AM, Marcus Denker wrote: > >> >> On Aug 27, 2010, at 11:02 AM, StÃ©phane Ducasse wrote: >> >>> We are not consistent: >>> >>> Â Â Â do we want >>> Â Â Â Â Â Â Â renameInstVar:to: >>> Â Â Â or >>> Â Â Â Â Â Â Â removeInstVarName: >>> Â Â Â Â Â Â Â Â Â Â Â I prefer that. >>> >>> We have addInstVarName: >>> Â Â Â -> should be addInstVarNamed: from my taste >>> >>> >>> Now we want to have first class instance variable in the near future so I would like to have >>> >>> Â Â Â addInstVar: aVariable >>> Â Â Â addInstVarNamed: aString >>> >>> What do you think? >>> >> >> Yes! >> >> >> -- >> Marcus Denker Â -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

Aug. 27, 2010

Re: [Pharo-project] hasInstanceVariableNamed: hasClassVariableNamed:

by StÃ©phane Ducasse

> *Cough* deprecate *cough* ;) what you got a flu :) Of course this is done and I would like to have a refactoring called renameDeprecate :) Lukas? :) Stef > > Cheers, > Henry > > On Aug 27, 2010, at 10:51 44AM, StÃ©phane Ducasse wrote: > >> for example >> we have >> addClassVarName: >> classVarNamed: >> classVarNamed:put: >> removeClassVarName: >> >> I will rename >> addClassVarName: >> removeClassVarName: >> >> to be >> addClassVarNamed: >> removeClassVarNamed: >> >> consistency.... >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 27, 2010

Re: [Pharo-project] class API question

by StÃ©phane Ducasse

done :) I could not let that like that. Stef On Aug 27, 2010, at 11:11 AM, Marcus Denker wrote: > > On Aug 27, 2010, at 11:02 AM, StÃ©phane Ducasse wrote: > >> We are not consistent: >> >> do we want >> renameInstVar:to: >> or >> removeInstVarName: >> I prefer that. >> >> We have addInstVarName: >> -> should be addInstVarNamed: from my taste >> >> >> Now we want to have first class instance variable in the near future so I would like to have >> >> addInstVar: aVariable >> addInstVarNamed: aString >> >> What do you think? >> > > Yes! > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 27, 2010

[Pharo-project] could we fix MorphicModel

by stephane ducasse

gary? Do you have surgeon knife? Because I do not see why slider need to depend on that wonderfully designed code. use: cachedSelector orMakeModelSelectorFor: selectorBody in: selectorBlock | selector | model ifNil: [^ nil]. cachedSelector ifNil: ["Make up selector from slotname if any" selector := (slotName ifNil: [selectorBody] ifNotNil: [slotName , selectorBody]) asSymbol. (model class canUnderstand: selector) ifFalse: [(self confirm: 'Shall I compile a null response for' , Character cr asString , model class name , '>>' , selector) ifFalse: [self halt]. model class compile: (String streamContents: [:s | selector keywords doWithIndex: [:k :i | s nextPutAll: k , ' arg' , i printString]. s cr; nextPutAll: '"Automatically generated null response."'. s cr; nextPutAll: '"Add code below for appropriate behavior..."'.]) classified: 'input events' notifying: nil]] ifNotNil: [selector := cachedSelector]. ^ selectorBlock value: selector

Aug. 27, 2010

Re: [Pharo-project] hasInstanceVariableNamed: hasClassVariableNamed:

by Henrik Johansen

*Cough* deprecate *cough* ;) Cheers, Henry On Aug 27, 2010, at 10:51 44AM, StÃ©phane Ducasse wrote: > for example > we have > addClassVarName: > classVarNamed: > classVarNamed:put: > removeClassVarName: > > I will rename > addClassVarName: > removeClassVarName: > > to be > addClassVarNamed: > removeClassVarNamed: > > consistency.... > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 27, 2010