- Pharo-dev - lists.pharo.org

Image Segment semantics and weakness

by Eliot Miranda

Hi All, I want to check my understanding of reference semantics for image segments as I'm close to completing the Spur implementation. Specifically the question is whether objects reachable only through weak pointers should be included in an image segment or not. Remember that an image segment is created from the transitive closure of an Array of root objects, the *segment roots*. i.e. we can think of an image segment as a set of objects created by tracing the object graph from the segment roots. The segment always includes the segment roots. Except for the roots, objects are excluded from the segment that are also reachable form the roots of the system (the *system roots*, effectively the root environment, Smalltalk, and the stack of the current process). Consider a weak array in the transitive closure that is not reachable from the system roots, and hence should be included in the segment. Objects referenced from that weak array may be in one of three categories - reachable from the system roots (and hence not to be included in the segment) - *not* reachable form the system roots, but reachable from the segment roots via strong pointers (and hence to be included in the segment) - *not* reachable form the system roots, *not* reachable from the segment roots via strong pointers Should this last category be included or excluded from the segment? I think that it makes no difference, and excluding them is only an optimization. The argument is as follows. Imagine that immediately after loading the image segment there is a garbage collection. That garbage collection will collect all the objects in the last category as they are only reachable from the weak arrays in the segment. Hence we are free to follow weak references as if they are strong when we create the image segment, leaving it to subsequent events to reclaim those objects. An analogous argument accounts for objects reachable from ephemerons. Is my reasoning sound? -- best, Eliot

Oct. 20, 2014

Use Komitter in MC Browser?

by Sean P. DeNigris

I hacked the MC Browser to open up a Changes window along-side my commit dialog. Then I realized we already have this (and a bit more) with Komitter. What if we just plug Komitter into the "Save" operation? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Use-Komitter-in-MC-Browser-tp4785411.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 19, 2014

Issue 14269 Komitter: Improve layout for long repo names

by Sean P. DeNigris

https://pharo.fogbugz.com/default.asp?14269 Right now, no matter how wide the Komitter window is, the repo drop down often too narrow to see the repo names: <http://forum.world.st/file/n4785409/Screenshot_2014-10-19_16.png> Fix in inbox: SLICE-Issue-14269-Komitter-Improve-layout-for-long-repo-names-SeanDeNigris.1 - Add vertical splitter and intially equal columns between commit message widget and author/repo widgets Ready for review. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-14269-Komitter-Improve-layout-for-long-repo-nam… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 19, 2014

Re: [Pharo-dev] Spec Understandability

by Sean P. DeNigris

Sean P. DeNigris wrote > What is one supposed to do with an error like this? > [snip] Besides error intractability, there is also a cost to understanding the system via exploration - a glorious benefit of Morphic. In the past, one only had to bring up halos on and inspect a button to see how to duplicate its action. Now, to see what happens when one presses Versionner's "Commit the project" button, you have to drill down in the inspector from aButtonXyzMorph -> model -> actionHolder -> value, a tedious and opaque process. Of course, I'm not in any way against Spec or its goals, just sharing my unfolding experience using it. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spec-Understandability-tp4778370p4785401.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 19, 2014

Re: [Pharo-dev] new Pharo Success story

by Ben Coman

stepharo wrote: > Hi > > we just published a new success story: Pharo at CSOB > > http://pharo.org/success > > And yes we are interested in your success stories > > Stef > > PS: big thanks to Tomas and CSOB for letting us making this public. > > Great news. Congrats to the CSOB development team. There are some really good news bites there... * Pharo 1.4 solution successfully passed security and penetration tests. * Pharo 1.4 solution was smoothly upgraded to Pharo 3.0 * Full solution developed in less than 3 months while estimates made by other teams were from one and half year to two full years!!! cheers -ben

Oct. 19, 2014

Re: [Pharo-dev] pharo works fine on yosemite

by kilon alios

thats great news, i am in the process of downloading Yosemite and I have my fingers crossed for many apps as this is the first time I install a new macos version so quickly after its release. Most likely I will be fine though. On Sun, Oct 19, 2014 at 2:16 PM, Max Leske <maxleske(a)gmail.com> wrote: > Iâve been developing with Yosemite for the last two weeks. There seems to > be one issue with older VMs that can lock up from time to time. Other than > that I havenât experienced any difference to Mavericks (except for the > nicer full screen view :) ) > > Cheers, > Max > > On 19.10.2014, at 12:57, phil(a)highoctane.be wrote: > > Cool. I am still on Lion and was considering moving to the new shiny one. > > Thx for the report. > > Phil > Le 19 oct. 2014 12:49, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > >> Hi, >> >> I just installed OS X Yosemite (10.10), and it looks like Pharo works >> just fine. >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > >

Oct. 19, 2014

Re: [Pharo-dev] pharo works fine on yosemite

by Max Leske

Iâve been developing with Yosemite for the last two weeks. There seems to be one issue with older VMs that can lock up from time to time. Other than that I havenât experienced any difference to Mavericks (except for the nicer full screen view :) ) Cheers, Max > On 19.10.2014, at 12:57, phil(a)highoctane.be wrote: > > Cool. I am still on Lion and was considering moving to the new shiny one. > > Thx for the report. > > Phil > > Le 19 oct. 2014 12:49, "Tudor Girba" <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> a Ã©crit : > Hi, > > I just installed OS X Yosemite (10.10), and it looks like Pharo works just fine. > > Cheers, > Doru > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow"

Oct. 19, 2014

Re: [Pharo-dev] pharo works fine on yosemite

by phil＠highoctane.be

Cool. I am still on Lion and was considering moving to the new shiny one. Thx for the report. Phil Le 19 oct. 2014 12:49, "Tudor Girba" <tudor(a)tudorgirba.com> a Ã©crit : > Hi, > > I just installed OS X Yosemite (10.10), and it looks like Pharo works just > fine. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Oct. 19, 2014

pharo works fine on yosemite

by Tudor Girba

Hi, I just installed OS X Yosemite (10.10), and it looks like Pharo works just fine. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

Oct. 19, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40311 Home: https://github.com/pharo-project/pharo-core

Oct. 19, 2014