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

Re: [Pharo-project] PointerFinder & PointerExplorer

by StÃ©phane Ducasse

Yes they did and we talked a lot about it. It took us 3-4 hours :) On Jun 12, 2010, at 3:29 PM, Mariano Martinez Peck wrote: > Hi Johan. Very nice you started with this. Once, I took that issue and understood what Mattew did in squeak: http://bugs.squeak.org/view.php?id=7158 > > I liked his solution but I was not completly agree, I don't remember why, thus. Did you look at it? any thoughts about that? > > cheers > > Mariano > > On Sat, Jun 12, 2010 at 10:33 AM, Johan Brichau <johan.brichau(a)uclouvain.be> wrote: > Issue #156 (http://code.google.com/p/pharo/issues/detail?id=156) states that PointerFinder and PointerExplorer both have issues leaving out some pointers. > > Andy and I have been looking at the implementation of PointerFinder and PointerExplorer in Pharo1.1 to fix this. > > We came to the decision to throw out PointerFinder, replace its uses to uses of PointerExplorer and move PointerFinder's #pointersTo* class methods to ProtoObject because: > - PointerFinder's (instance) behavior seems to be really old code that was not using the pointsTo: (primitive) method, while its #pointersTo* class methods were using the pointsTo: (primitive) method > - It also seems the instance behavior of PointerFinder was wrong (it did not give us all pointers *at all*) > - PointerExplorer offers the same functionality using a tree view and eventually used the #pointersTo* class methods of PointerFinder... > > The fix is in SLICE-PointerFinderRemove-AndyKellens.1 and should be for 1.2 > > Maybe anyone has another opinion? > > ---------------------------- > Johan Brichau > johan.brichau(a)uclouvain.be > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 12, 2010

[Pharo-project] [update 1.2] #12006

by StÃ©phane Ducasse

12006 ----- - Issue 1795: look for squeak everywhere. Thanks Veronica Stef

June 12, 2010

[Pharo-project] FW: Issue 2476 in pharo: ConnectionQueue broken in 1.0 and 1.1 beta

by Schwab,Wilhelm K

Marcus, I somewhat understand the logic of "if we didn't find it before this, it's not a problem now" but that attitude quickly leads to a trap. Part of why I did not find this sooner is that I have been struggling to adapt to metacello. I am not convinced that there is much information on how to use it, but there is certainly a lot of mis-information. The end result is a big hurdle to adopting new images. You are already producing 1.2. The core is at 1.1 RC - that's great! But here in the trenches, there is nothing approximating a dev image beta, and I can't figure out how to build it. Then I need a Seaside-enabled image on top of that. There is very little of value I can do with a release until Seaside is present. There is a growing tsunami of source code that I have to get into an image in order to be able to work. I built that process initially in terms of the web image; they are gone so I built it in terms of the dev image; now I can't even get that. Some stability (tenacity might be a better word) in the production of what is delivered to the user/developer would help me be a more aggressive tester. As it is, I am hacking the build process rather than applying it to reach a point that I can contribute to testing. In the extreme case, I could retreat to use Seaside's pre-made images and ignore the bleeding edge of Pharo, but that is not something I care to do. At a minimum, the unstable download section should contain a link to an "official" page that shows how to build the dev and web configurations. If we can't do that, work on 1.2 is premature. Back to 2476, it is quite possible that rydier's suggestion of removing the true return value will allow it to work. We are testing a new release, or should be. Does that not seem like a good time to introduce such a simple fix? Bill ________________________________________ From: pharo(a)googlecode.com [pharo(a)googlecode.com] Sent: Saturday, June 12, 2010 3:01 AM To: Schwab,Wilhelm K Subject: Re: Issue 2476 in pharo: ConnectionQueue broken in 1.0 and 1.1 beta Updates: Labels: -Milestone-1.1 Comment #6 on issue 2476 by marcus.denker: ConnectionQueue broken in 1.0 and 1.1 beta http://code.google.com/p/pharo/issues/detail?id=2476 In Pharo-dev 1.0 and 1.1 beta: not a show stopper for 1.1 -- You received this message because you are the owner of the issue. You may adjust your issue notification preferences at: https://code.google.com/hosting/settings

June 12, 2010

Re: [Pharo-project] [update 1.2] #12005

by Mariano Martinez Peck

2010/6/12 Marcus Denker <marcus.denker(a)inria.fr> > > On Jun 12, 2010, at 3:40 PM, Mariano Martinez Peck wrote: > > > > On Sat, Jun 12, 2010 at 3:34 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > >> 12005 >> ----- >> >> Redo the changes of 11400: >> Issue 2548: NewTestMorphTests>>#testAcceptContents fails >> > > There is something I don't understand. The idea is to have all green test > for a release. So, what happens with these tests in Pharo 1.1 ? How the > tests will be green? should these issues should be integrated also in 1.1 ? > > > This change is already in 1.1... I just added it to 1.2, too. > Ahh okok sorry, I was a little offline ;) I will do a a PharoDev 1.1 based in RC1 very soon.... monday or thuesday cheers mariano > > Marcus > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2010

Re: [Pharo-project] [update 1.2] #12005

by Marcus Denker

On Jun 12, 2010, at 3:40 PM, Mariano Martinez Peck wrote: > > > On Sat, Jun 12, 2010 at 3:34 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > 12005 > ----- > > Redo the changes of 11400: > Issue 2548: NewTestMorphTests>>#testAcceptContents fails > > There is something I don't understand. The idea is to have all green test for a release. So, what happens with these tests in Pharo 1.1 ? How the tests will be green? should these issues should be integrated also in 1.1 ? This change is already in 1.1... I just added it to 1.2, too. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 12, 2010

Re: [Pharo-project] [update 1.2] #12005

by Mariano Martinez Peck

On Sat, Jun 12, 2010 at 3:34 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > 12005 > ----- > > Redo the changes of 11400: > Issue 2548: NewTestMorphTests>>#testAcceptContents fails > There is something I don't understand. The idea is to have all green test for a release. So, what happens with these tests in Pharo 1.1 ? How the tests will be green? should these issues should be integrated also in 1.1 ? cheers mariano > Issue 2547: FilesStreamTest>>testPositionPastEndIsAtEnd > Issue 2506: Browsing hierarchy of Traits crashes OB > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2010

[Pharo-project] [update 1.2] #12005

by Marcus Denker

12005 ----- Redo the changes of 11400: Issue 2548: NewTestMorphTests>>#testAcceptContents fails Issue 2547: FilesStreamTest>>testPositionPastEndIsAtEnd Issue 2506: Browsing hierarchy of Traits crashes OB -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 12, 2010

Re: [Pharo-project] PointerFinder & PointerExplorer

by Mariano Martinez Peck

Hi Johan. Very nice you started with this. Once, I took that issue and understood what Mattew did in squeak: http://bugs.squeak.org/view.php?id=7158 I liked his solution but I was not completly agree, I don't remember why, thus. Did you look at it? any thoughts about that? cheers Mariano On Sat, Jun 12, 2010 at 10:33 AM, Johan Brichau <johan.brichau(a)uclouvain.be>wrote: > Issue #156 (http://code.google.com/p/pharo/issues/detail?id=156) states > that PointerFinder and PointerExplorer both have issues leaving out some > pointers. > > Andy and I have been looking at the implementation of PointerFinder and > PointerExplorer in Pharo1.1 to fix this. > > We came to the decision to throw out PointerFinder, replace its uses to > uses of PointerExplorer and move PointerFinder's #pointersTo* class methods > to ProtoObject because: > - PointerFinder's (instance) behavior seems to be really old code that was > not using the pointsTo: (primitive) method, while its #pointersTo* class > methods were using the pointsTo: (primitive) method > - It also seems the instance behavior of PointerFinder was wrong (it did > not give us all pointers *at all*) > - PointerExplorer offers the same functionality using a tree view and > eventually used the #pointersTo* class methods of PointerFinder... > > The fix is in SLICE-PointerFinderRemove-AndyKellens.1 and should be for 1.2 > > Maybe anyone has another opinion? > > ---------------------------- > Johan Brichau > johan.brichau(a)uclouvain.be > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 12, 2010

[Pharo-project] [update 1.2] #12004

by StÃ©phane Ducasse

12004 ----- - ScriptLoaderTest fixes - Issue 2487: Morph cleaning - Issue 2455: testIsAllDigits Stef

June 12, 2010

[Pharo-project] [ANN] Hudson for PharoCore

by Marcus Denker

http://rmod.lille.inria.fr/hudson/ Report for 1.1: http://rmod.lille.inria.fr/hudson/job/PharoCore1.1/lastBuild/testReport/ Report for 1.2: http://rmod.lille.inria.fr/hudson/job/PharoCore1.2/lastBuild/testReport/ -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 12, 2010