- Pharo-dev - lists.pharo.org

Re: [Pharo-project] PBenchmark as a general framework for benchmarking in Smalltalk (commit access)

by Alexandre Bergel

> Since the general idea is to write benchmarks like unit tests, how about 'SMark'/'SBench' instead of 'SUnit'? I like the idea. Actually, this is what I have done with HealthReportProducer. A benchmark is created by subclassing it and defining #metric* methods. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 14, 2011

Re: [Pharo-project] Issue 1836 in pharo: Adding dedicated accessors for VM parameters

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #13 on issue 1836 by marcus.d...(a)gmail.com: Adding dedicated accessors for VM parameters http://code.google.com/p/pharo/issues/detail?id=1836 (No comment was entered for this change.)

March 14, 2011

Re: [Pharo-project] Issue 1036 in pharo: Better interrupt handler registration

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #7 on issue 1036 by marcus.d...(a)gmail.com: Better interrupt handler registration http://code.google.com/p/pharo/issues/detail?id=1036 (No comment was entered for this change.)

March 14, 2011

Re: [Pharo-project] Issue 1507 in pharo: is LocatedMethod needed?

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #5 on issue 1507 by marcus.d...(a)gmail.com: is LocatedMethod needed? http://code.google.com/p/pharo/issues/detail?id=1507 (No comment was entered for this change.)

March 14, 2011

[Pharo-project] [Bug Tracker] fixed vs. fixedProposed...

by Marcus Denker

Hi, There was always the confusion of the meaning of "fixed", which actually had no clear meaning... I therefore added some weeks ago FixProposed --> this issue has a proposal of a fix, but there is no consensus that it's good FixToInclude ---> Please add to unstable ASAP This makes it clear what the status is. I now re-tagged all "fixed" issues as "FixProposed" and removed the "fixed" status. Next step: There are far too many items tagged "1.3". I think only a very select set of items should have that tag. -> FixToInclude -> Show stoppers ("If we release tomorrow, would this be a show stopper?") -> Failing tests -> Things people are actively working on. I will re-tag items... but I will turn off Email notification so that we don't get 130 mails. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 14, 2011

Re: [Pharo-project] Issue 953 in pharo: PackageInfo could be much faster

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #20 on issue 953 by marcus.d...(a)gmail.com: PackageInfo could be much faster http://code.google.com/p/pharo/issues/detail?id=953 (No comment was entered for this change.)

March 14, 2011

Re: [Pharo-project] Issue 1575 in pharo: optimize WeakKeyDictionary and subclasses for messagesends

by pharo＠googlecode.com

Updates: Status: Invalid Comment #3 on issue 1575 by marcus.d...(a)gmail.com: optimize WeakKeyDictionary and subclasses for messagesends http://code.google.com/p/pharo/issues/detail?id=1575 Weak* will be revisited soon. I close this.

March 14, 2011

Re: [Pharo-project] Issue 3817 in pharo: make Object >> error: deprecated

by pharo＠googlecode.com

Comment #5 on issue 3817 by stephane...(a)gmail.com: make Object >> error: deprecated http://code.google.com/p/pharo/issues/detail?id=3817 only :) and I'm sure that I fixed some of them already :). What would be good is to perform an analysis to see their usage.

March 14, 2011

Re: [Pharo-project] Issue 3606 in pharo: [1.1.2] [Failing Test] Undeclared in package shout

by pharo＠googlecode.com

Updates: Status: WontFix Comment #3 on issue 3606 by marcus.d...(a)gmail.com: [1.1.2] [Failing Test] Undeclared in package shout http://code.google.com/p/pharo/issues/detail?id=3606 1.1 is retired to the archives.

March 14, 2011

Re: [Pharo-project] Issue 3581 in pharo: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.1.2-DevImage Milestone-1.2-DevImage Comment #10 on issue 3581 by marcus.d...(a)gmail.com: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3581 Problem in 1.2 (1.1 we don't care)

March 14, 2011