- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] nil pointersTo size

by Yuriy Tymchuk

All âuninitialisedâ variables are pointing to nil. I think this is the case Uko On 03 Sep 2014, at 06:10, Ben Coman <btc(a)openinworld.com> wrote: > > I am curious... what does it mean that > nil PointersTo size is a large number? Intuitively I'd have thought the answer would be zero. > > Pharo build 40196 --> ~101,000 > Pharo build 30856 --> ~103,000 > Pharo build 20628 --> ~80,000 > Squeak 4.5 --> ~40,000 > > cheers -ben >

Sept. 3, 2014

nil pointersTo size

by Ben Coman

I am curious... what does it mean that nil PointersTo size is a large number? Intuitively I'd have thought the answer would be zero. Pharo build 40196 --> ~101,000 Pharo build 30856 --> ~103,000 Pharo build 20628 --> ~80,000 Squeak 4.5 --> ~40,000 cheers -ben

Sept. 3, 2014

Re: [Pharo-dev] [ANN] Pointer Detective

by Ben Coman

Sept. 3, 2014

Re: [Pharo-dev] [ANN] Pointer Detective

by Ben Coman

Thierry Goubier wrote: > Thanks Ben, > > I think this will be very helpfull :) Could you add a > ConfigurationOfPointerDetective in the meta repo to enable an easy > access? I will soon, but its a single mcz with no dependencies, so don't let that hold you back from trying it :) cheers -ben > > Thierry > > Le 02/09/2014 19:40, Ben Coman a Ã©crit : >> greetings all, >> >> I had an itch to scratch... I find it difficult using the tree list >> of the standard Pointer Explorer to track down why objects aren't >> garbage collected. I always fear I'm not going to notice getting >> caught in a reference loop. So I created a tool presenting an >> alternative view as a directed graph. The graph incrementally builds >> out from the target object as you explore it. Nodes are colourised to >> help manage complexity. >> >> The attached snapshot is produced from evaluating the following >> Workspace script... >> testObject := 'END5'. >> ref1 := { testObject. nil }. >> ref2 := { ref1 }. >> ref3 := PDTestResource new heldObject: ref2. >> ref1 at: 2 put: ref3. "note the reference loop this creates" >> PointerDetective openOn: testObject. >> >> Now I expect I'm duplicating something done before, but I couldn't >> find anything quickly and it was an opportunity for some goal direct >> learning of Morphic. Thanks to Roassal an option for a spring-force >> layout is provided. That code was copied rather than create a >> dependency, and might need to be rationalized later. >> The code is a bit rough from hacking around learning how to make >> things work, but its functional, so its time to get it out in the open. >> >> For more information please refer to the repository home page... >> http://smalltalkhub.com/#!/~BenComan/PointerDetective >> >> cheers -ben > > >

Sept. 3, 2014

Re: [Pharo-dev] Is IDE4PLC Pharo based?

by garduino

Sure! Apart of the video that show familiar windows, in the page says: "EstÃ¡ desarrollado sobre Pharo-Smalltalk 2.0" :) -- View this message in context: http://forum.world.st/Is-IDE4PLC-Pharo-based-tp4775897p4775901.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Sept. 2, 2014

Re: [Pharo-dev] [ANN] Pointer Detective

by Stephan Eggermont

Nice work! I'm getting inspired. Stephan

Sept. 2, 2014

Is IDE4PLC Pharo based?

by Sebastian Sastre

Anybody knows? https://news.ycombinator.com/item?id=8260594 sebastian o/ blog: http://sebastianconcept.com LinkedIn: http://www.linkedin.com/in/sebastiansastre github: https://github.com/sebastianconcept

Sept. 2, 2014

Re: [Pharo-dev] [ANN] Pointer Detective

by Camille Teruel

On 2 sept. 2014, at 21:37, Max Leske <maxleske(a)gmail.com> wrote: > You are my hero! I was just complaining about that to Doru at ESUG. This sort of tool should be part of the standard tool set so please keep on improving it and weâll try to convince someone to integrate it :) +1 > Max > > On 02.09.2014, at 19:40, Ben Coman <btc(a)openInWorld.com> wrote: > >> greetings all, >> >> I had an itch to scratch... I find it difficult using the tree list of the standard Pointer Explorer to track down why objects aren't garbage collected. I always fear I'm not going to notice getting caught in a reference loop. So I created a tool presenting an alternative view as a directed graph. The graph incrementally builds out from the target object as you explore it. Nodes are colourised to help manage complexity. >> >> The attached snapshot is produced from evaluating the following Workspace script... >> testObject := 'END5'. >> ref1 := { testObject. nil }. >> ref2 := { ref1 }. >> ref3 := PDTestResource new heldObject: ref2. >> ref1 at: 2 put: ref3. "note the reference loop this creates" >> PointerDetective openOn: testObject. >> >> Now I expect I'm duplicating something done before, but I couldn't find anything quickly and it was an opportunity for some goal direct learning of Morphic. Thanks to Roassal an option for a spring-force layout is provided. That code was copied rather than create a dependency, and might need to be rationalized later. >> The code is a bit rough from hacking around learning how to make things work, but its functional, so its time to get it out in the open. >> >> For more information please refer to the repository home page... >> http://smalltalkhub.com/#!/~BenComan/PointerDetective >> >> cheers -ben >> <PointerDetectiveExample1.png> > >

Sept. 2, 2014

Re: [Pharo-dev] [ANN] Pointer Detective

by Mariano Martinez Peck

Also, would be nice to filter out StrongPointerExplorerWrapper instances. On Tue, Sep 2, 2014 at 5:09 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > BTW , +1 to the ability of open an inspect on a node. > > > On Tue, Sep 2, 2014 at 5:05 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Hi Ben, >> >> Very nice tool! Thank you very much for it. >> >> Question....do you think it is possible to add a feature that it >> automatically builds the whole graph starting at target object until the GC >> root that is holding it? In Pharo, the GC root is the special object array >> (see #newSpecialObjectsArray). >> So the code should basically do a loop for #pointersTo and check if one >> of those pointers is directly one of the array. Or something like that >> like. >> Probably it will crash the VM hahaha. But it would be nice to track from >> a certain object up to the GC root and see all that path in graph :) >> >> >> >> >> >> On Tue, Sep 2, 2014 at 4:41 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >> wrote: >> >>> Oh yes, this is essential part of âworking with objectsâ. No? >>> >>> >>> On 02 Sep 2014, at 21:37, Max Leske <maxleske(a)gmail.com> wrote: >>> >>> > You are my hero! I was just complaining about that to Doru at ESUG. >>> This sort of tool should be part of the standard tool set so please keep on >>> improving it and weâll try to convince someone to integrate it :) >>> > >>> > Max >>> > >>> > On 02.09.2014, at 19:40, Ben Coman <btc(a)openInWorld.com> wrote: >>> > >>> >> greetings all, >>> >> >>> >> I had an itch to scratch... I find it difficult using the tree list >>> of the standard Pointer Explorer to track down why objects aren't garbage >>> collected. I always fear I'm not going to notice getting caught in a >>> reference loop. So I created a tool presenting an alternative view as a >>> directed graph. The graph incrementally builds out from the target object >>> as you explore it. Nodes are colourised to help manage complexity. >>> >> >>> >> The attached snapshot is produced from evaluating the following >>> Workspace script... >>> >> testObject := 'END5'. >>> >> ref1 := { testObject. nil }. >>> >> ref2 := { ref1 }. >>> >> ref3 := PDTestResource new heldObject: ref2. >>> >> ref1 at: 2 put: ref3. "note the reference loop this creates" >>> >> PointerDetective openOn: testObject. >>> >> >>> >> Now I expect I'm duplicating something done before, but I couldn't >>> find anything quickly and it was an opportunity for some goal direct >>> learning of Morphic. Thanks to Roassal an option for a spring-force layout >>> is provided. That code was copied rather than create a dependency, and >>> might need to be rationalized later. >>> >> The code is a bit rough from hacking around learning how to make >>> things work, but its functional, so its time to get it out in the open. >>> >> >>> >> For more information please refer to the repository home page... >>> >> http://smalltalkhub.com/#!/~BenComan/PointerDetective >>> >> >>> >> cheers -ben >>> >> <PointerDetectiveExample1.png> >>> > >>> > >>> >>> >>> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

Sept. 2, 2014

Re: [Pharo-dev] [ANN] Pointer Detective

by Mariano Martinez Peck

BTW , +1 to the ability of open an inspect on a node. On Tue, Sep 2, 2014 at 5:05 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > Hi Ben, > > Very nice tool! Thank you very much for it. > > Question....do you think it is possible to add a feature that it > automatically builds the whole graph starting at target object until the GC > root that is holding it? In Pharo, the GC root is the special object array > (see #newSpecialObjectsArray). > So the code should basically do a loop for #pointersTo and check if one of > those pointers is directly one of the array. Or something like that like. > Probably it will crash the VM hahaha. But it would be nice to track from a > certain object up to the GC root and see all that path in graph :) > > > > > > On Tue, Sep 2, 2014 at 4:41 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > >> Oh yes, this is essential part of âworking with objectsâ. No? >> >> >> On 02 Sep 2014, at 21:37, Max Leske <maxleske(a)gmail.com> wrote: >> >> > You are my hero! I was just complaining about that to Doru at ESUG. >> This sort of tool should be part of the standard tool set so please keep on >> improving it and weâll try to convince someone to integrate it :) >> > >> > Max >> > >> > On 02.09.2014, at 19:40, Ben Coman <btc(a)openInWorld.com> wrote: >> > >> >> greetings all, >> >> >> >> I had an itch to scratch... I find it difficult using the tree list >> of the standard Pointer Explorer to track down why objects aren't garbage >> collected. I always fear I'm not going to notice getting caught in a >> reference loop. So I created a tool presenting an alternative view as a >> directed graph. The graph incrementally builds out from the target object >> as you explore it. Nodes are colourised to help manage complexity. >> >> >> >> The attached snapshot is produced from evaluating the following >> Workspace script... >> >> testObject := 'END5'. >> >> ref1 := { testObject. nil }. >> >> ref2 := { ref1 }. >> >> ref3 := PDTestResource new heldObject: ref2. >> >> ref1 at: 2 put: ref3. "note the reference loop this creates" >> >> PointerDetective openOn: testObject. >> >> >> >> Now I expect I'm duplicating something done before, but I couldn't >> find anything quickly and it was an opportunity for some goal direct >> learning of Morphic. Thanks to Roassal an option for a spring-force layout >> is provided. That code was copied rather than create a dependency, and >> might need to be rationalized later. >> >> The code is a bit rough from hacking around learning how to make >> things work, but its functional, so its time to get it out in the open. >> >> >> >> For more information please refer to the repository home page... >> >> http://smalltalkhub.com/#!/~BenComan/PointerDetective >> >> >> >> cheers -ben >> >> <PointerDetectiveExample1.png> >> > >> > >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

Sept. 2, 2014