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

Re: [Pharo-project] SUnit History

by StÃ©phane Ducasse

so will you fix it? Alex? Stef > Hi Lukas, > > Thanks for your review. We made this in a couple of days. > You suggested some cool changes, indeed. > > Cheers, > Alexandre > > > On 1 Apr 2009, at 12:07, Lukas Renggli wrote: > >> I have a few questions to the authors of the SUnit History feature: >> >> 1. I noticed is that all the results are stored in a dictionary of >> TestResult mapping the classes to their last result. When I delete >> tests, these obsolete classes remain references from the dictionary >> and thus never get garbage collected. Why not save the history in a >> class-instance variable of the TestCase itself? That would even make >> the code much simpler. >> >> 2. Why to store the history of test results in nested dictionaries, >> sets and arrays? We have a nice TestResult object that remembers >> exactly the same information and additionally allows to do all kinds >> of queryies like #hasFailures, hasPassed, ... I see that there is one >> problem here: the current implementation of TestResult remembers the >> test case instances, and thus would reference potentially a lot of >> unnecessary state. Maybe TestResult should only remember the method >> references of the tests, instead of the test cases? I guess that >> would >> solve other problems people regularly report with SUnit as well. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 1, 2009

Re: [Pharo-project] Changing the size of a font

by StÃ©phane Ducasse

>> > that's why you are a Professor and I'm a student ;-) Ok luke. I just know that I feel stupid when I do not know something and that this is cool to collect these snippets :) Stef

April 1, 2009

Re: [Pharo-project] about the closure

by Adrian Lienhard

I would like to see the pattern "all tests always green" (except for expected failures, see below). Maybe this is too rigorous in practice since not everybody seems to care that much about tests. It would mean that no new updates are pushed in the stream until all tests that were broken by the previous update are fixed. Or even better, we would not integrate any code as long as it breaks a test. Anyway, I see the following two possibilities: - use SUnit's expected failures feature (see implementors of #expectedFailures) to marke tests we know are broken - create a wiki page to document currently broken tests I would use the former only for tests that document a bug that we don't know how to fix within the foreseeable future. The drawback of the wiki page is that it is prone to get out of date. Cheers, Adrian On Apr 1, 2009, at 19:00 , Michael Roberts wrote: > It would be good to document this knowledge of what is expected in our > test suites. Especially if some are known to fail. Is there a pattern > already in use? > E.g. Method comment, pragma, wiki page entry? If not what should we > adopt? > > Thanks mike > > On 4/1/09, Marcus Denker <denker(a)acm.org> wrote: >> >> On 01.04.2009, at 11:31, StÃ©phane Ducasse wrote: >> >>> >>> On Apr 1, 2009, at 11:12 AM, Lukas Renggli wrote: >>> >>>>> lukas is it normal that we get 3 tests yellow - did you get the >>>>> same >>>>> in your image? >>>> >>>> #testToDoOutsideTemp and #testWhileModificationBefore are broken. I >>>> don't think that should stop us from integrating the closures into >>>> Pharo. Most "industrial strength" Smalltalk implementations have >>>> many >>>> more closure bugs than Pharo. >>> >>> This is integrated already and this is good to have such great test >>> suites. >>> I will integrate them this evening. >>> >> >> Lukas' teste should be already in, I think. >> >> Marcus >> >> >> -- >> Marcus Denker -- denker(a)acm.org >> http://www.marcusdenker.de >> >> >> _______________________________________________ >> 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

April 1, 2009

Re: [Pharo-project] about the closure

by Michael Roberts

It would be good to document this knowledge of what is expected in our test suites. Especially if some are known to fail. Is there a pattern already in use? E.g. Method comment, pragma, wiki page entry? If not what should we adopt? Thanks mike On 4/1/09, Marcus Denker <denker(a)acm.org> wrote: > > On 01.04.2009, at 11:31, StÃ©phane Ducasse wrote: > >> >> On Apr 1, 2009, at 11:12 AM, Lukas Renggli wrote: >> >>>> lukas is it normal that we get 3 tests yellow - did you get the same >>>> in your image? >>> >>> #testToDoOutsideTemp and #testWhileModificationBefore are broken. I >>> don't think that should stop us from integrating the closures into >>> Pharo. Most "industrial strength" Smalltalk implementations have many >>> more closure bugs than Pharo. >> >> This is integrated already and this is good to have such great test >> suites. >> I will integrate them this evening. >> > > Lukas' teste should be already in, I think. > > Marcus > > > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 1, 2009

[Pharo-project] Interesting link

by Damien Cassou

Damien P just gave me this link: http://factor-language.blogspot.com/2009/04/sup-dawg-we-heard-you-like-smal… Might interest some of you -- Damien Cassou http://damiencassou.seasidehosting.st

April 1, 2009

Re: [Pharo-project] [ANN] VM for closures on pharo web site

by Damien Cassou

On Wed, Apr 1, 2009 at 2:48 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > So the new pharo closure image from Marcus [4] should work with > that too and I would rather see the standard Squeak VM linked on the page > if we have full closure support there. But I would mention Exupery Win32 VM > as another option. I really don't care :-). I did that because I didn't know the linked VM had closure support. -- Damien Cassou http://damiencassou.seasidehosting.st

April 1, 2009

Re: [Pharo-project] [ANN] VM for closures on pharo web site

by Mariano Martinez Peck

On Wed, Apr 1, 2009 at 5:29 AM, Damien Cassou <damien.cassou(a)gmail.com>wrote: > On Tue, Mar 31, 2009 at 11:16 PM, Bryce Kampjes > <bryce(a)kampjes.demon.co.uk> wrote: > > I was afraid that mentioning that would cause confusion. Exupery is a > > JIT written in Smalltalk, the compiler runs as a normal Smalltalk > > process in the image just like any other Smalltalk code. It needs a VM > > with a few hooks to allow the native code it generates to be executed. > > The VMs I provide have both those hooks and the closure bytecodes. > > Support for both Exupery and closures is in the VMs. > > > > Exupery itself is a normal Monticello package which is available via > > SqueakSource or Universes, if you haven't loaded it and started it then > > there is no risk. > > To summarize: the Exupery VM has closure support for closure images, > use them and things will work ok. Don't try to use the JIT or you will > have problem (but you won't do that accidentally so you shouldn't > care). > Yes. Perfect now. Thanks for this. Cheers, Mariano > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 1, 2009

Re: [Pharo-project] [ANN] #10262cl

by Dale Henrichs

----- "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> wrote: | It would be great. I mean Really great. | Even if we want to have a better OB based may be system having a fall | | back is really important Okay ... I'll take a crack at the old debugger... Dale

April 1, 2009

[Pharo-project] [ANN] VM for closures on pharo web site

by Torsten Bergmann

Hi Damien, >> damien could you edit a page on the wiki with a link to these vms? > >http://code.google.com/p/pharo/wiki/Downloads?tm=2 > I dont know why you linked to the Exupery VM for Win32 on this page? Maybe because Bryce wrote in [1] that his VM has the closure bytecodes compiled in too. But AFAIK closures were also already implemented in the official standard windows Squeak VM in 3.11.1 (see [2]) and there is now also a newer windows VM version from Andreas provided last week (see [3]). So the new pharo closure image from Marcus [4] should work with that too and I would rather see the standard Squeak VM linked on the page if we have full closure support there. But I would mention Exupery Win32 VM as another option. Andreas, Bryce - any comments? Thanks Torsten BTW: The exupery VM does not respond to ALT+F4 for me... [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-March/007233.html [2] http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-March/134710.ht… [3] http://lists.squeakfoundation.org/pipermail/squeak-dev/2009-March/135189.ht… [4] http://lists.gforge.inria.fr/pipermail/pharo-project/2009-March/007220.html -- Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss fÃ¼r nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a

April 1, 2009

Re: [Pharo-project] [ANN] VM for closures on pharo web site

by Damien Cassou

On Wed, Apr 1, 2009 at 11:25 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > damien could you edit a page on the wiki with a link to these vms? http://code.google.com/p/pharo/wiki/Downloads?tm=2 -- Damien Cassou http://damiencassou.seasidehosting.st

April 1, 2009