- Pharo-dev - lists.pharo.org

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

Re: [Pharo-project] SUnit History

by Alexandre Bergel

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 1, 2009

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

by Damien Cassou

On Wed, Apr 1, 2009 at 11:24 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > you see damien :) that's why you are a Professor and I'm a student ;-) -- Damien Cassou http://damiencassou.seasidehosting.st

April 1, 2009

Re: [Pharo-project] SUnit History

by Lukas Renggli

3. Why the heck is the timestamp of the last run a String :-( On Wed, Apr 1, 2009 at 12:07 PM, Lukas Renggli <renggli(a)gmail.com> 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 > -- Lukas Renggli http://www.lukas-renggli.ch

April 1, 2009

[Pharo-project] SUnit History

by Lukas Renggli

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

April 1, 2009

[Pharo-project] [ANN] #10262cl

by Torsten Bergmann

On 01.04.2009, at 11:29, StÃ©phane Ducasse wrote: > Apparently this is realted to the bug I mentioned can you test the > fixes that mike sent. Yes it fixes the problem: '~test' encodeForHTTP now does not give an DNU anymore and OB is loading. Thx Torsten -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

April 1, 2009

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

by Marcus Denker

On 01.04.2009, at 11:29, StÃ©phane Ducasse wrote: > Apparently this is realted to the bug I mentioned can you test the > fixes that mike sent. I added that to the tracker: http://code.google.com/p/pharo/issues/detail?id=706 -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

April 1, 2009