- Pharo-dev - lists.pharo.org

[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

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

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

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

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

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

March 13, 2010

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 got: ConfigurationOfMetacello-DaleHenrichs.194. If I run now the -- Miguel CobÃ¡ http://miguel.leugim.com.mx

1 0

[Pharo-project] PluggableSet and KeyedSet serve the same purpose
by Niko Schwarz March 13, 2010

March 13, 2010

Hi list, the purpose of PluggableSet and KeyedSet is the same: they're both sets where the equivalence relation is overwritten by a block. One of the two should be removed. What do you think? Cheers, Niko -- http://scg.unibe.ch/staff/Schwarz twitter.com/nes1983 Tel: +41 076 235 8683

2 1

March 13, 2010

11262 ----- - Issue 2018: remove #clone (thanks Philippe) Stef Philippe is getting champion in removing Object method (the competition is getting tough)

1 0

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

March 13, 2010

Igor wrote: >If such kind of collections didn't existed over more than >30 years of smalltalk existance, what makes you think >that there a big interest in having them today? Memory. Without the memory to use them, the need was not there. >Of course, they could occupy some niche, but i doubt >that they will replace an existing classes in a day-to-day use. In a 64 bit system, it is not a niche. You simply need a set of collection classes that work well with millions an tens of millions of elements, not just 100.000s. >Besides, many projects implementing own kinds of collections, >specific to their needs. That is exactly what you want to avoid. I've had to implement these collections too often. Stephan

2 1

March 13, 2010

11260 ----- - Issue 2111: Object>>initialExtent - Issue 2133: AllChangeSets size == 8482 ... and I m not explicitly using ChangeSets (part one) - Issue 2106: NullStream bern sprinters....

1 0