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

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/… 1 regressions found. Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

Aug. 26, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… 1 regressions found. Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

Aug. 26, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linu… 1 regressions found. Tests.Release.ReleaseTest.testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits

Aug. 26, 2013

Re: [Pharo-dev] what is the new way to do Smalltalk at: #MyClass?

by Norbert Hartl

Am 26.08.2013 um 10:56 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > On Aug 25, 2013, at 9:40 AM, Camille Teruel <camille.teruel(a)gmail.com> wrote: > >> >> On 24 aoÃ»t 2013, at 19:20, Camillo Bruni wrote: >> >>> We have now: >>> >>> String >> #asClass >>> String >> #asClassIfAbsent: >>> String >> #asClassIfPresent: >> >> I don't understand why we need this new way. >> Is it just to avoid calling 'Smalltalk globals at: #MyClass'? > > exactly > >> Because these names are confusing, and the 'as' prefix suggests a conversion while it's an access (with indirection but still a mere access). >> And #asClass has no sender. >> If you think 'Smalltalk globals at: #MyClass' is really too long to type, lets just create a new global ThisEnvironment := Smalltalk globals. > > this was already discussed. With #asClass and relatives what you have is a better abstraction jut because you are decoupled of "Smalltalk globals", it is not a big win now, but it open doors to better designs with environments, etc. > At least, that was my understanding when the issue arise at the beginning. > I just find it strange that an as* selector might _not_ return anything needing a #asClassIfAbsent: selector. While I'm understanding the intention it does not fit in my had. To me it worsens the understanding of as* conversion selectors. Norbert > >> >> >>> >>> On 2013-08-24, at 17:55, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: >>>> I prefer to evaluate >>>> >>>> Smalltalk globals classNamed: #MyClass >>>> >>>> Fernando >>>> >>>> On Sat, Aug 24, 2013 at 11:57 AM, StÃ©phane Ducasse >>>> <stephane.ducasse(a)inria.fr> wrote: >>>>> >>>>> Is it >>>>> >>>>> asClass? >>>>> >>>>> Stef >>>>> >>>> >>> >>> >> >> > >

Aug. 26, 2013

Re: [Pharo-dev] what is the new way to do Smalltalk at: #MyClass?

by Damien Cassou

On Mon, Aug 26, 2013 at 11:26 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > I do not see why because it means we can override #asClass: in each class and do whatever we want. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Aug. 26, 2013

Re: [Pharo-dev] what is the new way to do Smalltalk at: #MyClass?

by Esteban Lorenzano

I do not see why On Aug 26, 2013, at 11:14 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Mon, Aug 26, 2013 at 10:56 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> this was already discussed. With #asClass and relatives what you have is a better abstraction jut because you are decoupled of "Smalltalk globals", it is not a big win now, but it open doors to better designs with environments, etc. >> At least, that was my understanding when the issue arise at the beginning. > > > thinking about it, wouldn't "self asClass: #MyClass" be easier to > adapt for environments/packages than "#MyClass asClass" ? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Aug. 26, 2013

[update 3.0] #30342

by Marcus Denker

30342 ----- 11421 Update Athens from config https://pharo.fogbugz.com/f/cases/11421 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Athens-Text-MarcusDenker.7.di… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Athens-Morphic-MarcusDenker.2… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Athens-Examples-MarcusDenker.… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Athens-Core-MarcusDenker.36.d… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Athens-CairoPools-MarcusDenke… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Athens-Cairo-MarcusDenker.49.… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Athens-Balloon-MarcusDenker.1…

Aug. 26, 2013

Re: [Pharo-dev] what is the new way to do Smalltalk at: #MyClass?

by Damien Cassou

On Mon, Aug 26, 2013 at 10:56 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > this was already discussed. With #asClass and relatives what you have is a better abstraction jut because you are decoupled of "Smalltalk globals", it is not a big win now, but it open doors to better designs with environments, etc. > At least, that was my understanding when the issue arise at the beginning. thinking about it, wouldn't "self asClass: #MyClass" be easier to adapt for environments/packages than "#MyClass asClass" ? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Aug. 26, 2013

Re: [Pharo-dev] what is the new way to do Smalltalk at: #MyClass?

by Esteban Lorenzano

On Aug 25, 2013, at 9:40 AM, Camille Teruel <camille.teruel(a)gmail.com> wrote: > > On 24 aoÃ»t 2013, at 19:20, Camillo Bruni wrote: > >> We have now: >> >> String >> #asClass >> String >> #asClassIfAbsent: >> String >> #asClassIfPresent: > > I don't understand why we need this new way. > Is it just to avoid calling 'Smalltalk globals at: #MyClass'? exactly > Because these names are confusing, and the 'as' prefix suggests a conversion while it's an access (with indirection but still a mere access). > And #asClass has no sender. > If you think 'Smalltalk globals at: #MyClass' is really too long to type, lets just create a new global ThisEnvironment := Smalltalk globals. this was already discussed. With #asClass and relatives what you have is a better abstraction jut because you are decoupled of "Smalltalk globals", it is not a big win now, but it open doors to better designs with environments, etc. At least, that was my understanding when the issue arise at the beginning. Esteban > > >> >> On 2013-08-24, at 17:55, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: >>> I prefer to evaluate >>> >>> Smalltalk globals classNamed: #MyClass >>> >>> Fernando >>> >>> On Sat, Aug 24, 2013 at 11:57 AM, StÃ©phane Ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> Is it >>>> >>>> asClass? >>>> >>>> Stef >>>> >>> >> >> > >

Aug. 26, 2013

[update 3.0] #30341

by Marcus Denker

Aug. 26, 2013