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

[Pharo-project] [update 1.1] #11267
by StÃ©phane Ducasse March 13, 2010

March 13, 2010

11267 ----- fixing startup list of SmalltalkImage Thanks philippe and fernando for the great help. Now we will have to fix the registration mechanism. Stef

1 0

[Pharo-project] Fwd: updated startup script
by StÃ©phane Ducasse March 13, 2010

March 13, 2010

Begin forwarded message: > From: Philippe Marschall <philippe.marschall(a)gmail.com> > Date: March 13, 2010 7:29:52 PM GMT+01:00 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: updated startup script > > The following script opens two collections. The first is the one we > should send #initialize to. The second ones are the problematic ones > that don't implement #initialize, currently only InputEventSensor. > > classes := ((SystemNavigation default allCallsOn: > #'addToStartUpList:') collect: [ :e | e methodClass ]), > ((SystemNavigation default allCallsOn: #'addToStartUpList:after:') > collect: [ :e | e methodClass ]). > startClassNames := classes collect: [ :n | n instanceSide name ]. > (Smalltalk class classVarNamed: 'StartUpList') do: [ :s | > startClassNames remove: s ifAbsent: [] ]. > > classes := ((SystemNavigation default allCallsOn: > #'addToShutDownList:') collect: [ :e | e methodClass ]), > ((SystemNavigation default allCallsOn: #'addToShutDownList:after:') > collect: [ :e | e methodClass ]). > stopClassNames := classes collect: [ :n | n instanceSide name ]. > (Smalltalk class classVarNamed: 'ShutDownList') do: [ :s | > stopClassNames remove: s ifAbsent: [] ]. > > (startClassNames, stopClassNames) asSet asSortedCollection inspect. > ((startClassNames, stopClassNames) asSet asSortedCollection reject: [ :c | > (Smalltalk globals classNamed: c) class includesSelector: #initialize > ]) inspect

1 0

[Pharo-project] Issue 2140 - Packages dirty after running the tests
by Jorge Ressia March 13, 2010

March 13, 2010

Hi, When running tests, Changes are being applied to the system and Packages are left dirty. Some of these issues have been solved in Name: Tests-JorgeRessia.128 Author: JorgeRessia Time: 13 March 2010, 2:39:13 pm UUID: ae807242-d429-497f-916d-8d53aeffe87a Ancestors: Tests-JorgeRessia.127 - Executing Compilation test silently - ATestCase in Tests-Traits created a class, now is done silently - In ChangeSetClass a DeleteMe package was created and the PackageOrganizer and the MCWorkingCopy were dirty. Now the package is deleted. Issues still remain to be fixed in: - Tests-Traits - Tests-Monticello - Tests-PrimCallController - Tests-SystemChangeNotifier Cheers, Jorge

2 1

[Pharo-project] fun VM crash
by StÃ©phane Ducasse March 13, 2010

March 13, 2010

Hi We have a fun crash. If we copy and paste a method from squeak to pharo, the VM crashes Stef and Philippe

1 4

[Pharo-project] Issue 2030 - fixed
by Jorge Ressia March 13, 2010

March 13, 2010

Hi, The shadowing was detected by the Encoder>>bindTemp: for method added by Traits. A new validation was added for detecting this special case and avoid the error. Name: SLICE-ShadowingOfTraitsIssue2030-JorgeRessia.2 Author: JorgeRessia Time: 13 March 2010, 4:34:47 pm UUID: b7513eee-36ef-4fac-b976-9169e7d94c1c Ancestors: SLICE-ShadowingOfTraitsIssue2030-JorgeRessia.1 Dependencies: Compiler-JorgeRessia.194, Tests-JorgeRessia.129 Cheers, Jorge

1 0

[Pharo-project] Problems with ConfigurationOfMetacello in PharoCore 10514
by Miguel Enrique CobÃ¡ Martinez March 13, 2010

March 13, 2010

Sorry, I pressed the button to early... full mail follows: Take a PharoCore 10508, update it with update stream to 10514. open a workspace and evaluate: Gofer it squeaksource: 'MetacelloRepository'; project: 'ConfigurationOfRFB'; load. Then ConfigurationOfRFB project latestVersion load It shows an error: Unable to resolve ConfigurationOfMetacello in method GoferPackageReference>>resolverWith: Installed packages: Gofer-Core-MarkusDenker.117 Gofer-Tests-MarkusDenker.116 ConfigurationOfRFB-tbn.4 Same happens with: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMagma'; load. ((Smalltalk at: #ConfigurationOfMagma) project version: '1.0r43') load: 'Tester' If I manually install Metacello (not bootstraped from gofer): Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfMetacello'; load. I get: ConfigurationOfMetacello-DaleHenrichs.194. If I run now the ConfigurationOfRFB project latestVersion load I get: Error: Unable to resolve Metacello-Core-DaleHenrichs.348 If I run ConfigurationOfMetacello loadLatestVersion I also get the error: Error: Unable to resolve Metacello-Core-DaleHenrichs.348 So, what should we do? I am seeing that ConfigurationOfMetacello>>version10beta24: has blessing #beta and uses package Metacello-Core-Dalehenrichs.349 but ConfigurationOfMetacello>>version10beta23: has blessing #beta and uses package Metacello-Core-Dalehenrichs.348 so, loadLatestVersion is not getting laste 1.0beta24 version but 1.0beta23 version for metacello Can you please check? Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

2 6

Re: [Pharo-project] Collection
by Stephan Eggermont March 13, 2010

March 13, 2010

Igor wrote: >Yes. Use right tool for to do job. >An OrderedCollection can't satisfy every possible combination of >tasks, which developer facing. So, these collections are currently missing. And as all current code is bound to the current implementations, switching implementation on size is the prefered approach. Stephan

3 2

March 13, 2010

11265 ----- - Issue 2136: Smalltalk and SmalltalkImage (part Two) rename protocol responsibilities distributed between SmalltalkImage and SystemDictionary Stef and Philippe

1 0

Re: [Pharo-project] collections
by Stephan Eggermont March 13, 2010

March 13, 2010

Levente wrote: >How bad do they perform? Do you have benchmarks? With a coll := OrderedCollection new. 1 to: 10000000 do: [:i | coll add: i]. a profile of: 1 to: 100 do: [:i | coll add: i beforeIndex: 10] here takes 1438 ms. Moving memory gets to be slow. All operations that start taking O(#elements) time are no longer funny. The usual thing to do is to start using multiple blocks of memory (like a BTree). Doubling size when growing is also not an acceptable strategy when getting close to total ram capacity. Stephan

3 2

March 13, 2010

11264 ----- - Issue 2136: Smalltalk and SmalltalkImage (part One) copy protocols of SystemDictionary to SmalltalkImage. I n particular, SmalltalkImage gets dictionary protocols. Smalltalk -> SmalltalkImage current stephane and philippe

1 0