- Pharo-dev - lists.pharo.org

[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

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

Jan. 17, 2010

The test is incompatible with new CompiledMethod trailer Use generate rather than generate: #(0 0 0 0) Then the method still fails because sending unimplemented #blockExtentsToTempRefs same for testBlockNumberingForInjectInto testTempNameAccessForInjectInto Nicolas

3 6

[Pharo-project] Putting Algernon and WorkingSet in a Dev image
by Mariano Martinez Peck Jan. 16, 2010

Jan. 16, 2010

I think both are really great tools and if people don't use them is mostly because they don't know that even they exist or how they work. What do you think about loading both tools in PharoDev? they are little tools and easy to install. Maybe we can give them a try during "one" PharoDev and if they don't like, they can just be don't included any more. Do you want to try them first ? For WorkginSet: read this mail: http://n2.nabble.com/ANN-WorkingSet-td4286093.html#a4286093 For Alegernon evaluate: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfAlgernon'; load. ((Smalltalk at: #ConfigurationOfAlgernon) project version: '0.9.1') load. (Smalltalk at: #Algernon) openWelcomeWorkspace For the lazy ones, this is what that workspace says: "Algernon is a productivity tool for Pharo programmers; your personal assistant for Pharo. Algernon aims to make programming in Pharo faster and more keyboard centric. It is a launcher and quick way to access any category, class, morph, or global variable in your image. Pressing shift-return anywhere brings up Algernon. Start typing a class name, a morph's name, a category, an object, global variable and a list of items is filtered as you type. Press return to perform the default action on that item, or press tab to see a list of possible actions. Algernon can also evaluate Smalltalk expressions. Simply bring up Algernon and type = to enter expression mode to have quick access or print the results. Usage: Press shift-return to bring up Algernon. Start typing a name, then press return to perform the default action on the item, or hit tab to see a list of possible actions, included, for example, open that class in a new browser. Press right arrow to drill into a class or category and see its methods or classes, respectively. Press ctrl-r to refresh if you add new items that need to be indexed." What do you think ? Mariano ps: +1 for me :)

5 18

[Pharo-project] Problem with OB compare versions - Issue 1033 again :(
by Mariano Martinez Peck Jan. 16, 2010

Jan. 16, 2010

Hi: In latest Dev version there is again this bug :( http://code.google.com/p/pharo/issues/detail?id=1033 The problem is that OBVersionBrowser DNU definitionPanel In previous versions OBBrowser has definitionPanel but in latest version it doesnt. I think the fix is as putting again: OBBrowser >> definitionPanel ^ panels detect: [:ea | ea isDefinition] ifNone: [self error: 'No definition panel configured'] Or maybe it should be in OBVersionBrowser ? Cheers Mariano

2 2

[Pharo-project] [update 1.1] #11165
by Marcus Denker Jan. 16, 2010

Jan. 16, 2010

11165 ----- Issue 1835: Use selectorsAndMethodsDo: Issue 1837: Correct some failing tests in Pharo 1.1 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [ANN] Pharo News Blog
by Adrian Lienhard Jan. 16, 2010

Jan. 16, 2010

Hi all, We've started a blog on the Pharo website: http://www.pharo-project.org/news The goal of this blog is to regularly publish interesting news about Pharo (maybe once or twice a month). This allows people who do not have the time to closely follow the mailing list to stay up to date. Hope you like it! Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

4 3

[Pharo-project] Pharo 1.1 failing tests testNewLineStartsIndentedWhenWrapped
by Nicolas Cellier Jan. 16, 2010

Jan. 16, 2010

If paragraph composition width is reduced by 24 instead of 20, the test works (taken from trunk) testNewLineStartsIndentedWhenWrapped "Checks whether the beginning of a new line starts at the indented position" | cb | para compositionRectangle: (0@0 extent: para width - 24@100); updateCompositionHeight. para clippingRectangle: (0@0 extent: 200@200). cb := para characterBlockForIndex: 8. self assert: cb top > 0. self assert: cb left = 24

2 1

[Pharo-project] Pharo 1.1 failing tests testToDoOutsideTempNotInlined
by Nicolas Cellier Jan. 16, 2010

Jan. 16, 2010

Sorry this is an effect of automatic move of temps inside blocks... testToDoOutsideTempNotInlined REQUIRES that | temp | be declared outside the block. Just revert to previous version from Lukas Nicolas

2 1