March 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] about the closure

by Lukas Renggli

> Furthermore I wrote an set of tests (see attachement). These tests > especially make sure that none of the optimizations destroy the > closure behavior. All existing Smalltalk implementations have some > bugs, even the commercial ones. I should note that these tests were written after a long discussion with Oscar on the exact ANSI Smalltalk block semantics. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 30, 2009

Re: [Pharo-project] Issue #684 Recent Morphic Changesets

by Rob Rothwell

Does the actual change set help? If so...here it is. Also, the only other things I have submitted have been the update button for the fonts, and that removal of Display-something-or-other for Michael... If the mail doesn't get there, let me know and I'll try again! Rob On Mon, Mar 30, 2009 at 5:54 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > ok excellent > I'm doing it right now > > On Mar 30, 2009, at 11:08 PM, Henrik Sperre Johansen wrote: > > > HaloMorphRefactoring was the changeset from Gary (which you > > mentioned in mail 17.3 you'd integrate ;) ), so shouldn't need any > > licence from Rob. > > He also mentioned PluggableTextMorph was a .cs from some while back > > (I don't remember from whom it came). > > > > And yes, I'll check if the update will remove the BorderedMorph > > areasRemainingToFill: completely :) > > > > Cheers, > > Henry > > > > On 30.03.2009 22:48, StÃ©phane Ducasse wrote: > >> Hi rob > >> > >> did you sign the license agreement? > >> If not please do it > >> Thanks > >> > >> Stef > >> On Mar 22, 2009, at 6:22 PM, Rob Rothwell wrote: > >> > >> > >>> Hi all, > >>> > >>> I got tired of filing in HaloMorphRefactoring and > >>> PluggableTextMorph- > >>> scrollSelectionIntoView with every new update, so I published a > >>> Morphic package Morphic-rob_rothwell.290 in the inbox with these > >>> changes after upgrading to version 10259. > >>> > >>> Just fixes the non-transparent HaloMorph and non-scrolling edit > >>> window when selecting text. > >>> > >>> Take care, > >>> > >>> Rob > >>> _______________________________________________ > >>> 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 > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 30, 2009

Re: [Pharo-project] Issue #684 Recent Morphic Changesets

by Rob Rothwell

Yes...but I can't find my email saying when I put it in the mail! I remember it cost less than a dollar, though, to send something all the way across the ocean! Rob On Mon, Mar 30, 2009 at 4:48 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Hi rob > > did you sign the license agreement? > If not please do it > Thanks > > Stef > On Mar 22, 2009, at 6:22 PM, Rob Rothwell wrote: > > > Hi all, > > > > I got tired of filing in HaloMorphRefactoring and PluggableTextMorph- > > scrollSelectionIntoView with every new update, so I published a > > Morphic package Morphic-rob_rothwell.290 in the inbox with these > > changes after upgrading to version 10259. > > > > Just fixes the non-transparent HaloMorph and non-scrolling edit > > window when selecting text. > > > > Take care, > > > > Rob > > _______________________________________________ > > 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 >

March 30, 2009

Re: [Pharo-project] Issue #684 Recent Morphic Changesets

by StÃ©phane Ducasse

ok excellent I'm doing it right now On Mar 30, 2009, at 11:08 PM, Henrik Sperre Johansen wrote: > HaloMorphRefactoring was the changeset from Gary (which you > mentioned in mail 17.3 you'd integrate ;) ), so shouldn't need any > licence from Rob. > He also mentioned PluggableTextMorph was a .cs from some while back > (I don't remember from whom it came). > > And yes, I'll check if the update will remove the BorderedMorph > areasRemainingToFill: completely :) > > Cheers, > Henry > > On 30.03.2009 22:48, StÃ©phane Ducasse wrote: >> Hi rob >> >> did you sign the license agreement? >> If not please do it >> Thanks >> >> Stef >> On Mar 22, 2009, at 6:22 PM, Rob Rothwell wrote: >> >> >>> Hi all, >>> >>> I got tired of filing in HaloMorphRefactoring and >>> PluggableTextMorph- >>> scrollSelectionIntoView with every new update, so I published a >>> Morphic package Morphic-rob_rothwell.290 in the inbox with these >>> changes after upgrading to version 10259. >>> >>> Just fixes the non-transparent HaloMorph and non-scrolling edit >>> window when selecting text. >>> >>> Take care, >>> >>> Rob >>> _______________________________________________ >>> 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 >

March 30, 2009

[Pharo-project] [ANN] 10262

by StÃ©phane Ducasse

hi tomorrow closures! Issue 648: Opening protocol browser results in a MessageNotUnderstood: CompiledMethod>>category CompiledMethod>>category by eric Issue 684: Recent Morphic Changesets Removed BorderedMorph>>areasRemainingToFill: Issue 691: integrate Setting System-Setting Issue 696: SuniGUi showing coverage SUnit coverage enhancement Issue 697: New Socket IPv6 new socket primitive and IPv6 changes Alain for setting it would be good - to have a bit more explanation of the design - to know if some of the widgets are setting specific Now we can start having a real layer for preference instead of spaghetti code and also remove the old browser. Stef

March 30, 2009

Re: [Pharo-project] about the closure

by StÃ©phane Ducasse

Thanks! On Mar 30, 2009, at 11:40 PM, Lukas Renggli wrote: > Eliots code comes with additional tests. > > Furthermore I wrote an set of tests (see attachement). These tests > especially make sure that none of the optimizations destroy the > closure behavior. All existing Smalltalk implementations have some > bugs, even the commercial ones. > > Another test is that the image can be completely recompiled and no > additional test fails. > > Then the Seaside tests are another good candidate, they depend heavily > on block behavior. And continuations extensively stress the context > implementation. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > <ClosureTests.st>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 30, 2009

Re: [Pharo-project] about the closure

by Lukas Renggli

Eliots code comes with additional tests. Furthermore I wrote an set of tests (see attachement). These tests especially make sure that none of the optimizations destroy the closure behavior. All existing Smalltalk implementations have some bugs, even the commercial ones. Another test is that the image can be completely recompiled and no additional test fails. Then the Seaside tests are another good candidate, they depend heavily on block behavior. And continuations extensively stress the context implementation. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 30, 2009

Re: [Pharo-project] about the closure

by StÃ©phane Ducasse

- do all kind of things with the system - checking the tests that failed Stef On Mar 30, 2009, at 11:17 PM, Michael Roberts wrote: > Hi stef > Apart from kicking the tyres, how best do we test the closure > integration? > > Thanks > Mike > > On 3/30/09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> hi guys >> >> we discussed a bit with marcus and we arrived to the conclusion that >> we want to push the changes >> in the stream and that we will fix the problems when they show up. >> Now what it means is that >> - we will do probably today >> -> produce a new image >> with non dirty packages >> >> -> produce some fixes to check if we can load them with MC. >> >> and make it roll :) >> >> BTW having closure is really great. the code is so much nicer. >> >> Stef >> >> _______________________________________________ >> 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 >

March 30, 2009

Re: [Pharo-project] about the closure

by Michael Roberts

Hi stef Apart from kicking the tyres, how best do we test the closure integration? Thanks Mike On 3/30/09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > hi guys > > we discussed a bit with marcus and we arrived to the conclusion that > we want to push the changes > in the stream and that we will fix the problems when they show up. > Now what it means is that > - we will do probably today > -> produce a new image > with non dirty packages > > -> produce some fixes to check if we can load them with MC. > > and make it roll :) > > BTW having closure is really great. the code is so much nicer. > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 30, 2009

Re: [Pharo-project] Issue #684 Recent Morphic Changesets

by Henrik Sperre Johansen

HaloMorphRefactoring was the changeset from Gary (which you mentioned in mail 17.3 you'd integrate ;) ), so shouldn't need any licence from Rob. He also mentioned PluggableTextMorph was a .cs from some while back (I don't remember from whom it came). And yes, I'll check if the update will remove the BorderedMorph areasRemainingToFill: completely :) Cheers, Henry On 30.03.2009 22:48, StÃ©phane Ducasse wrote: > Hi rob > > did you sign the license agreement? > If not please do it > Thanks > > Stef > On Mar 22, 2009, at 6:22 PM, Rob Rothwell wrote: > > >> Hi all, >> >> I got tired of filing in HaloMorphRefactoring and PluggableTextMorph- >> scrollSelectionIntoView with every new update, so I published a >> Morphic package Morphic-rob_rothwell.290 in the inbox with these >> changes after upgrading to version 10259. >> >> Just fixes the non-transparent HaloMorph and non-scrolling edit >> window when selecting text. >> >> Take care, >> >> Rob >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>

March 30, 2009