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

Mariano & Behavior>>methodDict
by ClÃ©ment Bera Aug. 9, 2013

Aug. 9, 2013

Hello Mariano and others, In Pharo there is a method: Behavior>>methodDict methodDict == nil ifTrue: [^ MethodDictionary new ]. ^ methodDict It seems (according to the latest author) that it is Mariano who changed it from: Behavior>>methodDict methodDict == nil ifTrue: [self error: 'MethodDict is nil']. ^ methodDict A comment is present: "The method dictionary of a class can be nil when we want to use the #cannotInterpret: hook. Indeed when a class dictionary is nil, the VM sends the message cannotInterpret: to the receiver but starting the look up in the superclass of the class whose method dictionary was nil. Now the system relies that when the message methodDict is sent to a class a method dictionary is returned. In order to prevent the complaints of tools and IDE unaware of this feature, we fool them by providing an empty MethodDictionary. This will hopefully work in most cases, but the tools will loose the ability to modify the behavior of this behavior. The user of #cannotInterpret: should be aware of this." Now my problem is when I do: MyClass methodDict: nil. MyClass new name. It crashes the image in latest Pharo 3. Mariano, do you have an idea on how to fix it ? I ask you because you are the latest author and it seems tat the bug comes from this method. Thanks for any answer.

3 2

[update 3.0] #30328
by StÃ©phane Ducasse Aug. 8, 2013

Aug. 8, 2013

1 0

Changes in the repositories for the VM
by Esteban Lorenzano Aug. 8, 2013

Aug. 8, 2013

Hi, Ok, we finally decided to make some changes longtime postponed, to improve our way of building the VM. Squeak guys are still using the old mechanism, so this just applies to Pharo and the continuous integration under the Pharo umbrella... but please notice that ANY vm flavor can be built with this source repository. The first change was to put all sources together. No more MCZ files to keep VMMaker and plugins and platform sources as a GIT repository. We are using filetree to keep source files, so is just like a different kind of monticello repository. With this, now a commit is atomic and the platform sources will be in sync with VMMaker sources. Also, that simplifies a lot the ConfigurationOfCog file, since the commit number is the version number... now we just need the baseline (not version anymore). So now you can checkout a version of the repository and do: ConfigurationOfCog loadGit. and that's all :) (from our point of view, this simplification is an huge advantage over the older process). The second change is just a relocation. Now the VM source lives in GitHub :) The reason of this move is because GitHub has a lot more functionality than the old Gitorious, also most of the people using filetree are already using GitHub so is easier for them to fork, etc. Also, it is hyped so we wanted to be in that wave ;) The new repository can be found at: https://github.com/pharo-project/pharovm Cheers, Esteban

2 1

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Aug. 8, 2013

Aug. 8, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/… 7 regressions found. KernelTests.Classes.BehaviorTest.testBehaviorRespectsPolymorphismWithTraitBehavior KernelTests.Classes.MetaclassTest.testMetaclassAndTraitClassRespectsPolymorphismRules KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses Refactoring.Tests.Environment.RBBrowserEnvironmentTest.testNotEnvironment Refactoring.Tests.Environment.RBBrowserEnvironmentTest.testOrEnvironment Refactoring.Tests.Environment.RBBrowserEnvironmentTest.testRemoveSelectorByAndAndNot Tests.Release.ReleaseTest.testInstanceSideMethodsWithNilKeyInLastLiteral

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Aug. 8, 2013

Aug. 8, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… 7 regressions found. KernelTests.Classes.BehaviorTest.testBehaviorRespectsPolymorphismWithTraitBehavior KernelTests.Classes.MetaclassTest.testMetaclassAndTraitClassRespectsPolymorphismRules KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses Refactoring.Tests.Environment.RBBrowserEnvironmentTest.testNotEnvironment Refactoring.Tests.Environment.RBBrowserEnvironmentTest.testOrEnvironment Refactoring.Tests.Environment.RBBrowserEnvironmentTest.testRemoveSelectorByAndAndNot Tests.Release.ReleaseTest.testInstanceSideMethodsWithNilKeyInLastLiteral

1 0

[regression reporter]regression occurred
by no-reply＠ci.inria.fr Aug. 8, 2013

Aug. 8, 2013

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linu… 7 regressions found. KernelTests.Classes.BehaviorTest.testBehaviorRespectsPolymorphismWithTraitBehavior KernelTests.Classes.MetaclassTest.testMetaclassAndTraitClassRespectsPolymorphismRules KernelTests.Numbers.LargePositiveIntegerTest.testMethodsOfTheClassShouldNotBeRepeatedInItsSuperclasses Refactoring.Tests.Environment.RBBrowserEnvironmentTest.testNotEnvironment Refactoring.Tests.Environment.RBBrowserEnvironmentTest.testOrEnvironment Refactoring.Tests.Environment.RBBrowserEnvironmentTest.testRemoveSelectorByAndAndNot Tests.Release.ReleaseTest.testInstanceSideMethodsWithNilKeyInLastLiteral

1 0

[update 3.0] #30327
by Esteban Lorenzano Aug. 8, 2013

Aug. 8, 2013

30327 ----- 11144 Merge Latest NativeBoost with Pharo 3.0 https://pharo.fogbugz.com/f/cases/11144

1 0

Fwd: SmalltalkHub down
by Nicolas Cellier Aug. 8, 2013

Aug. 8, 2013

---------- Forwarded message ---------- From: Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> Date: 2013/8/8 Subject: SmalltalkHub down To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> http://smalltalkhub.com/ -> 502 Proxy Error

1 0

Please test: New PharoVM built
by Esteban Lorenzano Aug. 7, 2013

Aug. 7, 2013

Hi, Guille built a new vm with an attept of fixing the key combinations problem. Can you test it? http://files.pharo.org/vm/pharo/ (and pick the latest for your platform) Thanks, Esteban

3 2

becomeCompactSimplyAt: and Integer class>>initialize
by Martin Dias Aug. 7, 2013

Aug. 7, 2013

Hi 1) I'm working on an issue related to compact classes index and I discovered that behaviours implement #becomeCompactSimplyAt:, which has this comment: "Make me compact, but don't update the instances. *For importing segments* ." This made me think that it's no longer needed in the image since we removed ImageSegment. In other hand, I don't know why sender might decide if the instances of the class must be updated or not... do you? 2) The only users in Pharo 3 are in: Integer class >> initialize "Integer initialize" "Ensure we have the right compact class index" "LPI has been a compact class forever - just ensure basic correctness" (LargePositiveInteger indexIfCompact = 5) ifFalse:[ (Smalltalk compactClassesArray at: 5) ifNil:[LargePositiveInteger becomeCompactSimplyAt: 5] ifNotNil:[self error: 'Unexpected compact class setup']]. (LargeNegativeInteger indexIfCompact = 4) ifFalse:[ (Smalltalk compactClassesArray at: 4) ifNil:[LargeNegativeInteger becomeCompactSimplyAt: 4] ifNotNil:[self error: 'Unexpected compact class setup']]. Now, looking for other users of #indexIfCompact, I see that here is the only place in the image where compact indexes are checked/fixed. 3) I wonder if we should remove both #becomeCompactSimplyAt: and Integer class>>initialize. Thank you in advance. MartÃn

1 0