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

Re: [Pharo-project] Trait missing method isMetacelloConfig in Pharo 1.1

by StÃ©phane Ducasse

sounds good compromise indeed. Stef On Aug 3, 2010, at 7:31 PM, Mariano Martinez Peck wrote: > > > On Tue, Aug 3, 2010 at 7:29 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > we could add that to trait is this helps. > > > Not necessary. It will just have the *ob-metacello category so that with Monticello it is packaged inside the Mteacello packages. > just the same as Class >> isMetacelloConfig > > (I guess) > > > On Aug 3, 2010, at 7:25 PM, Mariano Martinez Peck wrote: > > > You spotted a Metacallo bug. Thanks for the report. > > > > The problem is (I think) that in > > > > OBCmdMetacello >> isActive > > ^ ((target isKindOf: OBClassNode) > > and: [ requestor isSelected: target ]) > > and: [ self selectedClass isMetacelloConfig ] > > > > > > selectClass can be a Trait, not necessary Behavior. > > > > If you see, Metacello implemented > > > > Class >>isMetacelloConfig > > > > ^false > > > > But nothing in Trait. So...you can just add it also in Traits or... > > > > Maybe moving that method to Behavior helps? I am not sure how Traits is implemented. Can you check? > > > > The problem is that Gemstone doesn't have Traits...thus problably why the bug exists :) > > > > Cheers > > > > Mariano > > > > > > > > On Tue, Aug 3, 2010 at 6:16 PM, Jochen Riekhof <lists(a)riekhof.de> wrote: > > Hi... > > > > just noticed that I get a walkback after creating a Trait and then opening the Context-Menu on the browser's classes list pane. It complains > > MessageNotUnderstood: Trait>>isMetacelloConfig > > > > Adding the missing method to Trait solves the issue. Probably it is just missing from {ob-metacello} package? > > > > Ciao > > > > ...Jochen > > > > > > _______________________________________________ > > 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 3, 2010

Re: [Pharo-project] Trait missing method isMetacelloConfig in Pharo 1.1

by Mariano Martinez Peck

On Tue, Aug 3, 2010 at 7:29 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > we could add that to trait is this helps. > > Not necessary. It will just have the *ob-metacello category so that with Monticello it is packaged inside the Mteacello packages. just the same as Class >> isMetacelloConfig (I guess) > On Aug 3, 2010, at 7:25 PM, Mariano Martinez Peck wrote: > > > You spotted a Metacallo bug. Thanks for the report. > > > > The problem is (I think) that in > > > > OBCmdMetacello >> isActive > > ^ ((target isKindOf: OBClassNode) > > and: [ requestor isSelected: target ]) > > and: [ self selectedClass isMetacelloConfig ] > > > > > > selectClass can be a Trait, not necessary Behavior. > > > > If you see, Metacello implemented > > > > Class >>isMetacelloConfig > > > > ^false > > > > But nothing in Trait. So...you can just add it also in Traits or... > > > > Maybe moving that method to Behavior helps? I am not sure how Traits is > implemented. Can you check? > > > > The problem is that Gemstone doesn't have Traits...thus problably why the > bug exists :) > > > > Cheers > > > > Mariano > > > > > > > > On Tue, Aug 3, 2010 at 6:16 PM, Jochen Riekhof <lists(a)riekhof.de> wrote: > > Hi... > > > > just noticed that I get a walkback after creating a Trait and then > opening the Context-Menu on the browser's classes list pane. It complains > > MessageNotUnderstood: Trait>>isMetacelloConfig > > > > Adding the missing method to Trait solves the issue. Probably it is just > missing from {ob-metacello} package? > > > > Ciao > > > > ...Jochen > > > > > > _______________________________________________ > > 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. 3, 2010

Re: [Pharo-project] Trait missing method isMetacelloConfig in Pharo 1.1

by StÃ©phane Ducasse

we could add that to trait is this helps. On Aug 3, 2010, at 7:25 PM, Mariano Martinez Peck wrote: > You spotted a Metacallo bug. Thanks for the report. > > The problem is (I think) that in > > OBCmdMetacello >> isActive > ^ ((target isKindOf: OBClassNode) > and: [ requestor isSelected: target ]) > and: [ self selectedClass isMetacelloConfig ] > > > selectClass can be a Trait, not necessary Behavior. > > If you see, Metacello implemented > > Class >>isMetacelloConfig > > ^false > > But nothing in Trait. So...you can just add it also in Traits or... > > Maybe moving that method to Behavior helps? I am not sure how Traits is implemented. Can you check? > > The problem is that Gemstone doesn't have Traits...thus problably why the bug exists :) > > Cheers > > Mariano > > > > On Tue, Aug 3, 2010 at 6:16 PM, Jochen Riekhof <lists(a)riekhof.de> wrote: > Hi... > > just noticed that I get a walkback after creating a Trait and then opening the Context-Menu on the browser's classes list pane. It complains > MessageNotUnderstood: Trait>>isMetacelloConfig > > Adding the missing method to Trait solves the issue. Probably it is just missing from {ob-metacello} package? > > Ciao > > ...Jochen > > > _______________________________________________ > 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. 3, 2010

[Pharo-project] About MethodContextTest

by StÃ©phane Ducasse

in Squeak there are a couple of MethodContextTest. do you remember why we removed them? Stef

Aug. 3, 2010

Re: [Pharo-project] Trait missing method isMetacelloConfig in Pharo 1.1

by Mariano Martinez Peck

You spotted a Metacallo bug. Thanks for the report. The problem is (I think) that in OBCmdMetacello >> isActive ^ ((target isKindOf: OBClassNode) and: [ requestor isSelected: target ]) and: [ self selectedClass isMetacelloConfig ] selectClass can be a Trait, not necessary Behavior. If you see, Metacello implemented Class >>isMetacelloConfig ^false But nothing in Trait. So...you can just add it also in Traits or... Maybe moving that method to Behavior helps? I am not sure how Traits is implemented. Can you check? The problem is that Gemstone doesn't have Traits...thus problably why the bug exists :) Cheers Mariano On Tue, Aug 3, 2010 at 6:16 PM, Jochen Riekhof <lists(a)riekhof.de> wrote: > Hi... > > just noticed that I get a walkback after creating a Trait and then opening > the Context-Menu on the browser's classes list pane. It complains > MessageNotUnderstood: Trait>>isMetacelloConfig > > Adding the missing method to Trait solves the issue. Probably it is just > missing from {ob-metacello} package? > > Ciao > > ...Jochen > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 3, 2010

Re: [Pharo-project] about value:

by StÃ©phane Ducasse

I found the problem.... some changes where missing from eliot. There were in the pending list. and will be integrated in the next batch. Stef On Aug 3, 2010, at 7:13 PM, StÃ©phane Ducasse wrote: > Henrik apparently this is coming from this change but from > > - Issue 2617: Fix restart in blocks in debugger. Thanks Henrik Johanssen. > > I should have run the tests.... since this was introduced in 12075 (lazy me). > > Stef > > On Aug 3, 2010, at 7:00 PM, StÃ©phane Ducasse wrote: > >> Henrik >> >> I integrated your value, value: cleans and I get such kind of error now. >> stackp = 2 and not zero. >> I'm puzzled. because I thought that the other code was not executed since it was covered by a primitive >> that would do the right job. >> >> >> pushArgs: args "<Array>" from: sendr "<ContextPart>" >> "Helps simulate action of the value primitive for closures. >> This is used by ContextPart>>runSimulated:contextAtEachStep:" >> >> stackp ~= 0 ifTrue: >> [self error: 'stack pointer should be zero!']. >> closureOrNil ifNil: >> [self error: 'context needs a closure!']. >> args do: [:arg| self push: arg]. >> 1 to: closureOrNil numCopiedValues do: >> [:i| >> self push: (closureOrNil copiedValueAt: i)]. >> sender := sendr >> _______________________________________________ >> 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. 3, 2010

Re: [Pharo-project] about value:

by StÃ©phane Ducasse

Henrik apparently this is coming from this change but from - Issue 2617: Fix restart in blocks in debugger. Thanks Henrik Johanssen. I should have run the tests.... since this was introduced in 12075 (lazy me). Stef On Aug 3, 2010, at 7:00 PM, StÃ©phane Ducasse wrote: > Henrik > > I integrated your value, value: cleans and I get such kind of error now. > stackp = 2 and not zero. > I'm puzzled. because I thought that the other code was not executed since it was covered by a primitive > that would do the right job. > > > pushArgs: args "<Array>" from: sendr "<ContextPart>" > "Helps simulate action of the value primitive for closures. > This is used by ContextPart>>runSimulated:contextAtEachStep:" > > stackp ~= 0 ifTrue: > [self error: 'stack pointer should be zero!']. > closureOrNil ifNil: > [self error: 'context needs a closure!']. > args do: [:arg| self push: arg]. > 1 to: closureOrNil numCopiedValues do: > [:i| > self push: (closureOrNil copiedValueAt: i)]. > sender := sendr > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 3, 2010

[Pharo-project] [update 1.2] #12078

by StÃ©phane Ducasse

12078 ----- - Issue 2661: File name correction for unix to allow. Thanks Eliot Miranda, German Ardino. - Issue 2122: superclassOrder: is defined on Changeset. Now defined on Class. Thanks Steven Freeman. - Fixed OSPlatform vmVersion

Aug. 3, 2010

[Pharo-project] about value:

by StÃ©phane Ducasse

Henrik I integrated your value, value: cleans and I get such kind of error now. stackp = 2 and not zero. I'm puzzled. because I thought that the other code was not executed since it was covered by a primitive that would do the right job. pushArgs: args "<Array>" from: sendr "<ContextPart>" "Helps simulate action of the value primitive for closures. This is used by ContextPart>>runSimulated:contextAtEachStep:" stackp ~= 0 ifTrue: [self error: 'stack pointer should be zero!']. closureOrNil ifNil: [self error: 'context needs a closure!']. args do: [:arg| self push: arg]. 1 to: closureOrNil numCopiedValues do: [:i| self push: (closureOrNil copiedValueAt: i)]. sender := sendr

Aug. 3, 2010

[Pharo-project] Strange Smalltalk vmVersion

by StÃ©phane Ducasse

Hi john Smalltalk getSystemAttribute: 1004 returns 'Squeak3.8.1 of ''28 Aug 2006'' [latest update: #6747] Squeak VM 4.2.4b1' do you know how we can fix that? Stef

Aug. 3, 2010