June 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] graph of object references

by Tudor Girba

Thanks, I will give it a try. Cheers, Doru On 2 Jun 2012, at 22:14, Mariano Martinez Peck wrote: > > > On Sat, Jun 2, 2012 at 10:10 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I would need to debug memory leaks (maybe induced by announcements), and for that I am thinking to use a graph of object references. > > I guess this would be easily possible with Fuel. If I have an object, how would I go about doing this? > > Hi Doru. Maybe this helps: > > http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.8/Documentation/… > > (look at the end) > > cheers > > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Don't give to get. Just give." > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > -- www.tudorgirba.com "Sometimes the best solution is not the best solution."

June 2, 2012

[Pharo-project] Pharo-2.0-Tests Â» 32,mac - Build # 109 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

June 2, 2012

[Pharo-project] Pharo-2.0-Tests Â» 32,linux - Build # 109 - Still Failing!

by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr

June 2, 2012

[Pharo-project] [update 2.0] #20105

by StÃ©phane Ducasse

20105 ----- Issue 6011: avoiding MCWorkingCopy allManagers expressions http://code.google.com/p/pharo/issues/detail?id=6011

June 2, 2012

Re: [Pharo-project] graph of object references

by Mariano Martinez Peck

On Sat, Jun 2, 2012 at 10:10 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I would need to debug memory leaks (maybe induced by announcements), and > for that I am thinking to use a graph of object references. > > I guess this would be easily possible with Fuel. If I have an object, how > would I go about doing this? > Hi Doru. Maybe this helps: http://rmod.lille.inria.fr/web/pier/software/Fuel/Version1.8/Documentation/… (look at the end) cheers > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Don't give to get. Just give." > > > > > > > -- Mariano http://marianopeck.wordpress.com

June 2, 2012

[Pharo-project] graph of object references

by Tudor Girba

Hi, I would need to debug memory leaks (maybe induced by announcements), and for that I am thinking to use a graph of object references. I guess this would be easily possible with Fuel. If I have an object, how would I go about doing this? Cheers, Doru -- www.tudorgirba.com "Don't give to get. Just give."

June 2, 2012

[Pharo-project] [update 2.0] #20104

by StÃ©phane Ducasse

20104 ----- Issue 6010: Fixing RPackageMCSynchronisationTests http://code.google.com/p/pharo/issues/detail?id=6010 Thanks Guillermo Polito to happily hacking with Stephane. This is funnier when we are two. Pair fixing is cool.

June 2, 2012

Re: [Pharo-project] Method protocol nitpick

by StÃ©phane Ducasse

I would like to recategorise systematically methods. Would be good to propose some rules and apply automatically. Stef On Jun 2, 2012, at 7:42 PM, Sean P. DeNigris wrote: > There are many test methods categorized as "testing". "Testing" means e.g. > #isEmpty. "tests" (which is also used for test methods) would be better... > > Sean > > -- > View this message in context: http://forum.world.st/Method-protocol-nitpick-tp4632925.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

June 2, 2012

Re: [Pharo-project] Method protocol nitpick

by Frank Shearar

On 2 June 2012 18:42, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > There are many test methods categorized as "testing". "Testing" means e.g. > #isEmpty. "tests" (which is also used for test methods) would be better... > > Sean I usually put tests in a "testing - foo" category. Tests for #isEmpty would thus be in "testing - testing". Kind've lame, but it does avoid conflating behaviour and tests in the same category, while still allowing categorising of tests. (It's not universally true, but most categories are -ing words. "instance creation", "initialize-release" are obvious counterexamples, but otherwise we have "enumerating", "accessing", "testing", ...) frank

June 2, 2012

[Pharo-project] Method protocol nitpick

by Sean P. DeNigris

There are many test methods categorized as "testing". "Testing" means e.g. #isEmpty. "tests" (which is also used for test methods) would be better... Sean -- View this message in context: http://forum.world.st/Method-protocol-nitpick-tp4632925.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 2, 2012