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

[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

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

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

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

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

[Pharo-project] [update] #10513
by Adrian Lienhard March 13, 2010

March 13, 2010

10513 ----- Issue 2102: Fix the fact that local temp can shadow silently instance var (thanks Jorge and Lukas!) Running all tests I get: 7137 run, 7120 passes, 17 expected failures, 0 failures, 0 errors, 0 unexpected passes :) Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

1 0

[Pharo-project] Smalltalk -> SmalltalkImage
by StÃ©phane Ducasse March 13, 2010

March 13, 2010

http://code.google.com/p/pharo/issues/detail?id=2136 any code is welcome :) Stef

1 0

Re: [Pharo-project] Collections
by Stephan Eggermont March 12, 2010

March 12, 2010

Stef wrote: > - are there some collections that would be cool to improve? > - are there some collections that would be cool to have and that we do not have yet? All collections with an Array as backing store do not perform well in a large memory setting. That's not only a problem in a 64-bit image. Stephan

2 1

[Pharo-project] Collection >> collectDistinct: ??
by Mariano Martinez Peck March 12, 2010

March 12, 2010

Hi. I was needing something like the SQL select distinct, that doesn't take into account repeated objects. I didn't found anything useful in Collection, and thus, I have implemented this: Collection >> collectDistinct: aBlock collectDistinct: aBlock "Evaluate aBlock with each of the receiver's elements as the argument. Collect the resulting values into a Set, thus repeated objects will not be present. Answer the new collection." | newSet | newSet := self species new asSet. self do: [:each | newSet add: (aBlock value: each)]. ^ newSet Is there a better way ? Do you think it make sense to put this in Pharo ? Cheers Mariano

9 16

[Pharo-project] We applied!!!
by Mariano Martinez Peck March 12, 2010

March 12, 2010

See the final application at: http://gsoc2010.esug.org/application.html. See final project ideas at: http://gsoc2010.esug.org/ideas.html It seems that we managed to activate our whole community to propose a record number of projects in a record short time this year. We namely have 35 project ideas (comparing to 15 in 2009, 18 in 2008, 24 in 2007) Proposed projects seem also of a high quality and this won't get unnoticed by Google, we can be sure. So, let we keep fingers crossed for a few days until Thursday, 16.March for Google to decide... Thanks to all for the project submissions, ideas, feedback and corrections! Janko and Mariano

2 1