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

[Pharo-project] About metacello meta repository and persistency of code
by StÃ©phane Ducasse Jan. 17, 2010

Jan. 17, 2010

Hi guys something I would really like to be able to have is that projects described using metacello and explicitly targetting for pharo are also saved in a specific repository in addition to their own projects. This way I would like to have a possible archive of all the projects described because I saw some sources like the one of salty pickles disappeared and you cannot load or browse old code. Right now I imagine that most of the projects are either on squeak source or ob or lukas one. Now with Gofer it should be easy to copy files around. Let me know what you think but I really hate to get a deadlink when I'm looking for something. This way it also ensures that the metacatalog is always complete. Stef

3 3

[Pharo-project] Pharo 1.1 failing tests testAllLocalCallsOn
by Nicolas Cellier Jan. 17, 2010

Jan. 17, 2010

testAllLocalCallsOn " self debug: #testAllLocalCallsOn " | set | set := Array allLocalCallsOn: #printOn:. self assert: (set asArray = #('WeakActionSequence printOn:' 'Object fullPrintString' 'Array printOn:' 'SequenceableCollection asStringWithCr' 'Behavior printOn:' 'Class fileOutPool:onFileStream:' 'Object printStringLimitedTo:' 'Collection printNameOn:' 'ActionSequence printOn:' 'FixedIdentitySet printOn:')). "This is a bit strange that allLocalCallsOn: returns a list of string!" This one is bad for two reasons: 1) it relies on an arbitrary order in Set. For example, just change default size of sets and the order will change. Eventually you could test set = #() asSet but see 2) 2) it relies on a particular snapshot of pharo and prevent pharo from evolving. Moreover, if a user adds its own sender of printOn: in an extension or a subclass, this will make the test fail... Such test should create a class hierarchy dedicated to the test with a know set of senders and test Either correct it or remove it. Nicolas

2 3

[Pharo-project] [bug] 1.0-10505 Saving image kills version browsers
by Martin McClure Jan. 17, 2010

Jan. 17, 2010

It looks like if you browse versions of a method, and save the image while the versions browser is open, this sets the source pointers in all of the versions in the browser to nil. Then you get a DNU if you click on any of the versions. Workaround: Close the bad version browser, open a new one. Regards, -Martin

3 3

[Pharo-project] SystemWindow updatablePanes ivar
by Igor Stasenko Jan. 17, 2010

Jan. 17, 2010

Hello, I completely lost in the logic of this thing. why a SystemWindow cares about something called panes? What if my window don't having/needs any of them? Why Object cares about #updateListsAndCodeIn: aWindow ??? If model is updated, then it should just send #changed, or self changed: #myPaneFoo and if SystemWindow's pane is dependent, it will be updated. What the point in using #verifyContents... This thing needs to be cleaned up. -- Best regards, Igor Stasenko AKA sig.

2 3

[Pharo-project] About versions on PharoInbox
by Miguel Enrique CobÃ¡ Martinez Jan. 17, 2010

Jan. 17, 2010

During the uploading of the mcz of Morphic to PharoInbox http://code.google.com/p/pharo/issues/detail?id=1841 I used a 10506 image. The software update gave 0 files and the Monticello browser showed: Morphic-MarkusDenker.392 my changes generated: Morphic-MiguelCoba.395 But when opening the PharoInbox I saw that there are versions like Morphic-nice.494 Morphic-TorstenBergmann.492 Morphic-AlainPlantec.490 and they have date as close as January 13, 2010. But the image has a version very old (or so appears by the version number) and my changes was based in MarkusDenker.392. Can someone explain this? Will this affect the integration of my change to PharoCore? Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

4 4

[Pharo-project] NewCompiler load on PharoCore
by Miguel Enrique CobÃ¡ Martinez Jan. 17, 2010

Jan. 17, 2010

Hi Markus, what is the correct way to load NewCompiler in a PharoCore image. I am loading with: Gofer it squeaksource: 'NewCompiler'; package: 'NewCompiler'; load. But it has dependencies on SmaCCParserError. Then looking at the NewCompilerLoader >> loadPackages loadPackages self loadLatestPackage: 'AST-Core' from: 'http://www.squeaksource.com/rb/'. " self loadLatestPackage: 'SmaCC-' from: 'http://www.squeaksource.com/SmaccDevelopment/'. self loadLatestPackage: 'NewParser-' from: 'http://www.squeaksource.com/AST/'." self loadLatestPackage: 'NewCompiler-' from: 'http://www.squeaksource.com/NewCompiler/'. "Preferences setPreference: #compileUseNewCompiler toValue: true. Compiler recompileAll." "no, not working yet" so this are all the dependencies? Has NewCompiler teste on PharoCore? Is there a gofer script to load it? Or better a Metacello configuration? If you can give me the dependencies I can create the Metacello configuration. Right now I am creating the configurations for Magma and through WriteBarrier, they depend on NewCompiler. Thanks -- Miguel CobÃ¡ http://miguel.leugim.com.mx

10 32

[Pharo-project] PrStef renamed to ProfStef
by laurent laffont Jan. 17, 2010

Jan. 17, 2010

So now it's Gofer new squeaksource: 'ProfStef'; package: 'ProfStef'; load. Laurent

1 0

[Pharo-project] [ANN 1.1] prebuilt core#11165
by Marcus Denker Jan. 17, 2010

Jan. 17, 2010

http://gforge.inria.fr/frs/download.php/25199/PharoCore-1.1-11165-UNSTABLE.… -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Pharo 1.0 & 1.1 failing tests testFinalizationOfEquals
by Nicolas Cellier Jan. 17, 2010

Jan. 17, 2010

I wrote this test pre-closure. The problem with closures is that they are optimized to retain a pointer to the values of outer temporary variable they use when activated. Thus the BlockClosures forAnyTwoEqualObjects ofDifferentIdentity registeringAnActionAtFinalizationForEachObject all refer to 'hello' pointed by o1 and its copy pointed by o2. In other words, o1 and o2 are not the single pointers to the String 'hello' and its copy. thenForcingFinalizationOfObjects only clean o1 and o2, but omit to clean the closures that still point to 'hello'... Thus, 'hello' is not finalized. One possibility is to also clean the closures pointing to 'hello'. But now the code is tricky... It's aim was to be simple damned :) Nicolas here is a corrected version : testFinalizationOfEquals "self debug: #testFinalizationOfEquals" | finalizationProbe o1 o2 forAnyTwoEqualObjects ofDifferentIdentity registeringAnActionAtFinalizationForEachObject thenForcingFinalizationOfObjects implyBothRegisteredActionsAreExecuted | finalizationProbe := Set new. o1 := 'hello' copy. o2 := 'hello' copy. forAnyTwoEqualObjects := [o1 = o2]. ofDifferentIdentity := [o1 ~~ o2]. registeringAnActionAtFinalizationForEachObject := [ o1 toFinalizeSend: #add: to: finalizationProbe with: 'first object finalized'. o2 toFinalizeSend: #add: to: finalizationProbe with: 'second object finalized']. thenForcingFinalizationOfObjects := [ forAnyTwoEqualObjects := ofDifferentIdentity := registeringAnActionAtFinalizationForEachObject := nil. o1 := o2 := nil. Smalltalk garbageCollect]. implyBothRegisteredActionsAreExecuted := [finalizationProbe size = 2]. self assert: forAnyTwoEqualObjects; assert: ofDifferentIdentity; should: [ registeringAnActionAtFinalizationForEachObject value. thenForcingFinalizationOfObjects value. implyBothRegisteredActionsAreExecuted value].

3 7

[Pharo-project] System -> About in Dev images
by Mariano Martinez Peck Jan. 17, 2010

Jan. 17, 2010

Hi folks: If you take a Dev image and go to " System->About " you get something like: PharoCore1.0rc1 Latest update: #10505 However, I would like to show something like this for example: Pharo1.0-10505-rc1dev10.01.1 PharoCore1.0rc1 Latest update: #10505 Do you know how we can change this? How can I set that name when building a PharoDev image? Is this related to SystemVersion ?? We need to have this fixed for the official 1.0 release. Cheers Mariano

5 23