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

Re: [Pharo-project] Issue 2787 in pharo: better test runner
by pharo＠googlecode.com March 27, 2011

March 27, 2011

Updates: Status: Closed Comment #2 on issue 2787 by marcus.d...(a)gmail.com: better test runner http://code.google.com/p/pharo/issues/detail?id=2787 added to http://code.google.com/p/pharo/wiki/IdeasToImplement

1 0

Re: [Pharo-project] Issue 2524 in pharo: Debugger code completion should take into account the types of the objects that are actually assigned to variables
by pharo＠googlecode.com March 27, 2011

March 27, 2011

Updates: Labels: -Milestone-1.2-DevImage Comment #4 on issue 2524 by marcus.denker: Debugger code completion should take into account the types of the objects that are actually assigned to variables http://code.google.com/p/pharo/issues/detail?id=2524 (No comment was entered for this change.)

1 1

[Pharo-project] test crashing the cog vm
by Tudor Girba March 26, 2011

March 26, 2011

Hi, Alex recently wrote a test in Moose that seems to crash the Cog VM at least on Mac. How to reproduce: - download the following image http://dl.dropbox.com/u/18323746/Tmp/moose-crashing-cog-jit.zip - execute the following code in the workspace (already provided in the image) cls := Class new superclass: MooseElement; yourself. cls compileSilently: 'mooseName ^ 1/0'. element := cls new. - I used all of the followings and they all crashed: https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog%20Mac%20Cocoa/4/art… https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/StackVM%20Mac%20Cocoa/2… http://www.mirandabanda.org/files/Cog/VM/VM.r2370/Cog.app.tgz http://www.mirandabanda.org/files/Cog/VM/VM.r2361/Cog.app.tgz The strange thing is that the crash only happens when we subclass MooseElement, but not another class. Could someone take a look? Cheers, Doru -- www.tudorgirba.com "Every thing should have the right to be different."

8 28

Re: [Pharo-project] Issue 2841 in pharo: Heap equality should be transitive
by pharo＠googlecode.com March 26, 2011

March 26, 2011

Comment #1 on issue 2841 by nicolas....(a)gmail.com: Heap equality should be transitive http://code.google.com/p/pharo/issues/detail?id=2841 If I download the code from Squeak trunk, it will break a lot of tests in HeapTest. (only due to the fact that I remove #species). I believe that assumptions made about Heap are not right. I wonder why the Heap should be considered as Sequenceable. Elements are partially sorted and the structure is more of a binary tree. Elements are not fully sorted, thus the order: - is not the order of the addition of elements, - is not independent of the order of addition. In fact, only the Heap head (first) is meaningfull. Thus testing some properties like #beginsWith: #endsWith: #at: #at:put: #reversed #copyFrom:to: etc... seems very fragile to me. Of course, that would mean moving the Heap one level up, directly under Collection, in order to cease undue inheritance of sequenceable API. What do you think ?

1 3

[Pharo-project] COG VM Locale?
by Hilaire Fernandes March 26, 2011

March 26, 2011

Is it likely it'll be fixed? If so when? I need to know so I can move to plan B if necessary. http://code.google.com/p/cog/issues/detail?id=1 Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

2 2

Re: [Pharo-project] who is using softSqueak and standard Squeak
by Marcus Denker March 26, 2011

March 26, 2011

On Sat, Mar 26, 2011 at 1:20 PM, Helene Bilbo <thereluctantprogrammer(a)fastmail.fm> wrote: > > "StÃ©phane Ducasseâ wrote: >> >> just out of curiosity who is using SoftSqueak and Standard Squeak theme? >> I know that lukas like colored windows now may be specific new style with >> this behavior could be done? >> > Hi, > i use them and like them a lot. > I am always reminded of that Dilbert strip: http://dilbert.com/strips/comic/2002-09-23/ Marcus -- Marcus DenkerÂ --Â denker(a)acm.org http://www.marcusdenker.de

1 0

Re: [Pharo-project] Issue 1854 in pharo: We remove CodeLoader
by pharo＠googlecode.com March 26, 2011

March 26, 2011

Updates: Status: Duplicate Mergedinto: 3818 Comment #13 on issue 1854 by marcus.d...(a)gmail.com: We remove CodeLoader http://code.google.com/p/pharo/issues/detail?id=1854 (No comment was entered for this change.)

1 1

March 26, 2011

13112 ----- - Issue 2704: Tests for broken withNoLineLongerThan: behavior. Thanks Nicolas Cellier and Andreas Raab. - Issue 3864: [Failing Test] 1.3 ImageSegmentTestExport. - Issue 3341: use #= for integer comparison instead of #==. Kernel Part. - Less overrides in the system: around 100 left. :( Thanks you all. I feel that we are getting to the point where we will really move forward. Stef

1 0

Re: [Pharo-project] Remove #class as a Compiler optimization
by Marcus Denker March 26, 2011

March 26, 2011

On Mar 25, 2011, at 5:46 PM, Camillo Bruni wrote: >> > > Arguing with absolute values is a bit dangerous: > > But it makes > 13ms / 17ms * 100% = 76% => 25% speed improvement! in COG > 50ms / 60ms * 100% = 83% => 17% faster > > So the impact is still quite big. But indeed I would be in favor of a normal message send... > And are you sure that your Doit is actually JITed in Cog? 1) always take the overhead of the loop into acount. Especially if it is a large percentage, it can make you "slowdown" seem very small even though it is huge. e.g. the overhead of the loop in your case should be *very* high. 90% of the execution time? 2) always make sure that you actually JIT. -> put it in a normal method in a class -> execute it at least 2 times Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 3

[Pharo-project] Issue 3864 in pharo: [Failing Test] 1.3 ImageSegmentTestExport
by pharo＠googlecode.com March 26, 2011

March 26, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3864 by marcus.d...(a)gmail.com: [Failing Test] 1.3 ImageSegmentTestExport http://code.google.com/p/pharo/issues/detail?id=3864 >>> Tests.System.ImageSegmentTestExport.testObsoleteFake37ClassesRefs >>> 0.167 139 >>> Tests.System.ImageSegmentTestExport.testSymbolsDuplicated 0.423 139 >>> Tests.System.ImageSegmentTestExport.testSaveClassAndNotTheMetaclass >>> 0.193 139 >>> Tests.System.ImageSegmentTestExport.testUniqueObjects 0.291 139 >>> Tests.System.ImageSegmentTestExport.testSaveAndLoadImageSegmentToDiskWithoutGC >>> >>> 0.22 139 >>> Tests.System.ImageSegmentTestExport.testSaveClassAndAlsoTheMetaclass >>> 0.112 139 >>> Tests.System.ImageSegmentTestExport.testStatesInExport 0.219 139 >>> Tests.System.ImageSegmentTestExport.testSegmentWordArraySize 0.093 139 >>> Tests.System.ImageSegmentTestExport.testSymbols 0.223 139 >>> Tests.System.ImageSegmentTestExport.testSaveAndLoadImageSegmentToDiskWithGC >>> >>> 0.22 139

1 2