- Pharo-users - lists.pharo.org

Re: [Pharo-users] implementing #release in a domain object

by Camillo Bruni

On 2013-06-27, at 01:08, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Sven & Camillo, > > Ok thanks. And using the PointerFinder is there a way to know which of > the pointers points to the SystemDictionary or Object someObject or > whereever the GC begins so one would not have to check every pointer for > every stubborn object. > > E.g. Lets say I've nil'ed the reference between the Navy and the ship so > its ready to go but a few of the soldiers on the ship have references to > other ships because their transfer papers weren't processed properly. > Running #pointersTo on those soldiers gives a large collection of > pointers. > > > How can I use the computer to filter that list to just those references > back to the root object? What do you mean by root object? In any case, if I'm not mistaken, this isn't that easy. Usually you have to manually track down and follow the objects in the PointerExplorer => Inspect an Object, right click, Explore Strong Pointers

June 27, 2013

Fwd: You've reached 100 views on SlideShare!

by StÃ©phane Ducasse

100 looks small :) http://www.slideshare.net/pharoproject Stef Begin forwarded message: > From: SlideShare <donotreply(a)slidesharemail.com> > Subject: You've reached 100 views on SlideShare! > Date: June 26, 2013 11:32:00 PM GMT+02:00 > To: board(a)pharo-project.org > > > > > > > Congrats, you have over 100 views on SlideShare! > > People like your stuff, so we'd like to encourage you to keep on sharing. Here's your reward from us for this decent feat â one month free trial of SlideShare PRO. > > > 1 > month > free PRO coupon > Code: > 9nrnq12xjv > View PRO benefits > â¦and redeem coupon. > > > > > * Terms and conditions > > Promotional offer is applicable only on monthly Silver and Gold SlideShare PRO accounts. One promotional offer per eligible subscriber. Expires in two weeks from the date of receipt. SlideShare PRO services are sold on a subscription basis and are automatically charged to your credit card at the beginning of each subscription period. Discount applies to the first month of a SlideShare PRO account subscription. After this period, you will be charged the standard rate on your renewal date unless or until you cancel your SlideShare PRO account. > > > From SlideShare, a LinkedIn company. Click here to follow your LinkedIn contacts on SlideShare now. > > We send these emails to help you get the most out of SlideShare. > You can change your email preferences or unsubscribe from SlideShare emails anytime. > Â© 2013 SlideShare, Inc., 490 2nd St., Suite #300, San Francisco, CA 94107, USA > >

June 27, 2013

Re: [Pharo-users] [Pharo-dev] Slide share

by StÃ©phane Ducasse

Ok so they try to influence the user by giving wrong information. I will continue to upload the slides then. Stef On Jun 27, 2013, at 8:58 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jun 26, 2013, at 9:13 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> http://www.slideshare.net/pharoproject/ >> > > >> Do you know if there are limits on the number of presentations that we can upload, because >> I see (get public on this presentation => go pro). >> So I wonder if I want to invest in slideshare. > > I think it is not limited for number of uploads. Just size of the file that is limited (to 100MB). > > More here: > http://www.slideshare.net/business/premium/plans > > Marcus > > >

June 27, 2013

Re: [Pharo-users] [Pharo-dev] Slide share

by Marcus Denker

On Jun 26, 2013, at 9:13 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > http://www.slideshare.net/pharoproject/ > > Do you know if there are limits on the number of presentations that we can upload, because > I see (get public on this presentation => go pro). > So I wonder if I want to invest in slideshare. I think it is not limited for number of uploads. Just size of the file that is limited (to 100MB). More here: http://www.slideshare.net/business/premium/plans Marcus

June 27, 2013

Re: [Pharo-users] Slide share

by StÃ©phane Ducasse

Thanks I only put 7 of them for now. I will continue. Stef On Jun 27, 2013, at 4:52 AM, Joachim Tuchel <jtuchel(a)objektfabrik.de> wrote: > Hi Stef > > I can only see 7 presentations. 4 of them are from 2013. > > Joachim > > StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> schrieb: > >> Hi guys >> >> we created a slideshare acount for pharo >> I added >> 2009 smalltalks slides >> 2011 ESUG >> 2013 Pharo Conference >> >> a new lecture >> Intro >> Model >> Syntax >> >> http://www.slideshare.net/pharoproject/ >> >> Can you tell me if you can see the 2013 pharo conference? >> Do you know if there are limits on the number of presentations that we can upload, because >> I see (get public on this presentation => go pro). >> So I wonder if I want to invest in slideshare. >>

June 27, 2013

Re: [Pharo-users] Slide share

by Joachim Tuchel

Hi Stef I can only see 7 presentations. 4 of them are from 2013. Joachim StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> schrieb: >Hi guys > >we created a slideshare acount for pharo >I added > 2009 smalltalks slides > 2011 ESUG > 2013 Pharo Conference > > a new lecture > Intro > Model > Syntax > > http://www.slideshare.net/pharoproject/ > >Can you tell me if you can see the 2013 pharo conference? >Do you know if there are limits on the number of presentations that we can upload, because >I see (get public on this presentation => go pro). >So I wonder if I want to invest in slideshare. >

June 27, 2013

Re: [Pharo-users] implementing #release in a domain object

by Paul DeBruicker

Sven & Camillo, Ok thanks. And using the PointerFinder is there a way to know which of the pointers points to the SystemDictionary or Object someObject or whereever the GC begins so one would not have to check every pointer for every stubborn object. E.g. Lets say I've nil'ed the reference between the Navy and the ship so its ready to go but a few of the soldiers on the ship have references to other ships because their transfer papers weren't processed properly. Running #pointersTo on those soldiers gives a large collection of pointers. How can I use the computer to filter that list to just those references back to the root object? Thanks for you help Paul On 06/26/2013 03:37 PM, Sven Van Caekenberghe wrote: > Paul, > > On 26 Jun 2013, at 23:47, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > >> Lets say I'm modeling a navy that is comprised of many ships each with >> their own soldiers and jobs. If I want one of the ships to be GC'd do I >> need to implement #release in the soldier and job objects and send it to >> each of those soldiers and jobs that live and work on the ship I want >> GC'd or is removing the references between the ship and the navy enough >> to have the whole ship (including its soldiers and jobs) GC'd? > > GC is automatic memory management. Whenever something is no longer reachable by following pointers from a a know starting set, the system dictionary, the stack and some other places, it automatically becomes garbage and the memory it occupies will be reused. > > Of course, if you keep a reference to an object, on purpose or by accident, the object will never become garbage and it will keep on occupying memory. Especially circular references can be hard to track. > > There are indeed a couple of common messages that are sometimes used to break possible references by nilling out instance variables etc. #close, #stop, #unregister and indeed #release. Often, these are also used to manage external resources (open files, sockets â¦). You can use any message to do this, there is no framework that you have to follow. > > And then there are also finalization and weak references, which are related, but more advanced. > > Sven >

June 26, 2013

Re: [Pharo-users] implementing #release in a domain object

by Sven Van Caekenberghe

Paul, On 26 Jun 2013, at 23:47, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Lets say I'm modeling a navy that is comprised of many ships each with > their own soldiers and jobs. If I want one of the ships to be GC'd do I > need to implement #release in the soldier and job objects and send it to > each of those soldiers and jobs that live and work on the ship I want > GC'd or is removing the references between the ship and the navy enough > to have the whole ship (including its soldiers and jobs) GC'd? GC is automatic memory management. Whenever something is no longer reachable by following pointers from a a know starting set, the system dictionary, the stack and some other places, it automatically becomes garbage and the memory it occupies will be reused. Of course, if you keep a reference to an object, on purpose or by accident, the object will never become garbage and it will keep on occupying memory. Especially circular references can be hard to track. There are indeed a couple of common messages that are sometimes used to break possible references by nilling out instance variables etc. #close, #stop, #unregister and indeed #release. Often, these are also used to manage external resources (open files, sockets â¦). You can use any message to do this, there is no framework that you have to follow. And then there are also finalization and weak references, which are related, but more advanced. Sven

June 26, 2013

Re: [Pharo-users] implementing #release in a domain object

by Camillo Bruni

ok I was not sure of how much you were aware of how the GC works :) second try: In your example it would be enough to cut the connection the ship, everything "aboard" will be GC'ed as well. Once you cut the connection to a subgraph of objects, and they are no longer reachable from the outside (root objects) the whole subgraph get's garbage collected. In your example: as soon as nobody references a ship anymore it gets garbage collected, as well as all objects that were only reachable via that ship. clearer? If not I suggest you quickly make your own little example. Note that with #allInstances you can see which objects are still around of a certain class, for instance: Dictionary allInstances On 2013-06-27, at 00:13, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > In Pharo2 Object (and many other classes) implement #release and > #release has many senders. So I don't understand how 'there is no such > thing as #release in Pharo'. I understand that the GC is a VM thing and > it does not send #release to the objects in the image. > > > IF in my hypothetical question the Navy object contains an ordered > collection of ships, and each ship is referenced in that collection and > also by all of its soldiers and jobs, to have my ship GC'd do I only > need to remove the reference to the ship in the Navy object (at which > point the ship becomes detached and self contained amalgamation of > soldiers and jobs) or do I have to have each soldier and job dereference > the ship too? > > > > > On 06/26/2013 03:05 PM, Camillo Bruni wrote: >> There is no such thing as #release in Pharo. If you want your objects >> to be garbage collected just make sure to remove all references to it. >> You simply assign nil to instance variables which previously held such >> and object. >> >> Does that answer your question? >> >> On 2013-06-26, at 23:47, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >>> Lets say I'm modeling a navy that is comprised of many ships each with >>> their own soldiers and jobs. If I want one of the ships to be GC'd do I >>> need to implement #release in the soldier and job objects and send it to >>> each of those soldiers and jobs that live and work on the ship I want >>> GC'd or is removing the references between the ship and the navy enough >>> to have the whole ship (including its soldiers and jobs) GC'd? >> > >

June 26, 2013

Re: [Pharo-users] implementing #release in a domain object

by Paul DeBruicker

In Pharo2 Object (and many other classes) implement #release and #release has many senders. So I don't understand how 'there is no such thing as #release in Pharo'. I understand that the GC is a VM thing and it does not send #release to the objects in the image. IF in my hypothetical question the Navy object contains an ordered collection of ships, and each ship is referenced in that collection and also by all of its soldiers and jobs, to have my ship GC'd do I only need to remove the reference to the ship in the Navy object (at which point the ship becomes detached and self contained amalgamation of soldiers and jobs) or do I have to have each soldier and job dereference the ship too? On 06/26/2013 03:05 PM, Camillo Bruni wrote: > There is no such thing as #release in Pharo. If you want your objects > to be garbage collected just make sure to remove all references to it. > You simply assign nil to instance variables which previously held such > and object. > > Does that answer your question? > > On 2013-06-26, at 23:47, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >> Lets say I'm modeling a navy that is comprised of many ships each with >> their own soldiers and jobs. If I want one of the ships to be GC'd do I >> need to implement #release in the soldier and job objects and send it to >> each of those soldiers and jobs that live and work on the ship I want >> GC'd or is removing the references between the ship and the navy enough >> to have the whole ship (including its soldiers and jobs) GC'd? >

June 26, 2013