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

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

by Michael Roberts

ok great thanks. That works. Do we record somewhere what we expect the baseline of the test results to be in the image? Mike

March 31, 2009

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

by Bryce Kampjes

On Tue, 2009-03-31 at 19:03 -0100, Mariano Martinez Peck wrote: > The Exupery VMs have closures. You can use them on both Windows and > Linux. I released them here to help people test the image > without > needing to compile their own VMs. > > Ok, so, I didn't understood what you said: > > "P.S. Don't use Exupery in a closure image, that'll probably crash. > The > issue is both Exupery and closures use the "unused" slot in > MethodContext. I'll update Exupery to work with closure images as part > of the next release." 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. Bryce

March 31, 2009

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

by Lukas Renggli

> on the closure related note, what is perhaps interesting in a workspace is > > values := (1 to: 5) collect: [:each | [each] ]. > values collect: [:each | each value] > --> #(1 2 3 4 5) That's correct. > | i | > values := (1 to: 5) collect: [:each | > Â Â Â Â Â Â Â Â Â Â Â Â i := each. > Â Â Â Â Â Â Â Â Â Â Â Â [i] ]. > values collect: [:each | each value] > -->#(5 5 5 5 5) That behavior is correct. i is defined outside the block, thus it refers to the current number which is 5. > values := OrderedCollection new. > 1 to: 5 do: [:i | values add: [i] ]. > values collect: [:each | each value] > --> an OrderedCollection(6 6 6 6 6) That's a bug, but already fixed by Eliot. I don't know why the patch is not included with the image? Load the attachement. The two other failing tests are actually failing in most Smalltalk, even in commercial ones. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 31, 2009

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

by Dale Henrichs

----- "Michael Roberts" <mike(a)mjr104.co.uk> wrote: | guys I have done a quick test of the closure image, with the mac VM | on | the inria page. | | I think it is probably unrelated but the old debugger in the core | image is severely broken. Could someone please remind me | | 1) what we were going to do with the old debugger. I know there is | work going on in the dev image on the new one... what is the | strategy? | | 2) i'd appreciate if someone could see if there is a bug report that | confirms this behaviour below. Otherwise I will at least file a | report. Candidate bug report is #329 but I am not sure exactly if it | is what I see. | | steps | 1. run ClosureTests in the test runner | 2. 3 fail, so click on testToDoWithArgument | 3. hit debug | 4. restart the test method | 5. step over the to:do:. you only enter the loop block once, BUG #1 | ? | 6. step into the assertValues: method as it is highlighted | 7. highlight now enters the loop again, not into the utility method. | BUG #2 ? | 8. carefully step until you get into the assert method, if you do | this | wrong a new notifier pops up BUG #3. if you kill this you get error | unwind pop up that you can't ever kill. BUG #4 ? | | basically this debugger is unusable and I think it has been for some | time. I'm sure I commented in the past. so please give me your | thoughts on the old debugger and live issues in the tracker. Do | people not notice, because they generally load the OB debugger? I | want to know where to concentrate my efforts. I'm not sure we should | develop the old debugger too much, but at one point it did work in | squeak. I'm sure the unwind notifier bug predates pharo. surely it's | not just me. my vote would be to attempt to fix the debugger, so we | have one in the core image that works, and then perhaps leave it | alone.. or we promote the new one into it when it can be a | replacement. | | on the closure related note, what is perhaps interesting in a | workspace is | | values := (1 to: 5) collect: [:each | [each] ]. | values collect: [:each | each value] | --> #(1 2 3 4 5) | | | i | | values := (1 to: 5) collect: [:each | | i := each. | [i] ]. | values collect: [:each | each value] | -->#(5 5 5 5 5) | | values := OrderedCollection new. | 1 to: 5 do: [:i | values add: [i] ]. | values collect: [:each | each value] | --> an OrderedCollection(6 6 6 6 6) | | I know the second and third gives non closure related result, but I | don't know if the first one shows valid closure or not. | | Anyway please direct and I will keep testing. If there is consensus to fix the old debugger, and noone else steps to the plate, I would be willing to see what I could do in getting the old debugger functional with the ClosureTests... Dale

March 31, 2009

[Pharo-project] Changing the size of a font

by Alexandre Bergel

Hi All, Is there a not-so-slow way to change programmatically the size of a font? I tried 'TextStyle defaultFont pointSize: 8', but I have no idea what pointSize really does. It has to do with the real font. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 31, 2009

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

by Mariano Martinez Peck

On Tue, Mar 31, 2009 at 6:51 PM, Bryce Kampjes <bryce(a)kampjes.demon.co.uk>wrote: > On Tue, 2009-03-31 at 18:42 -0100, Mariano Martinez Peck wrote: > > > > > Ok. Thanks. But, now I wonder, is there a linux and windows vm > > somehere with closure so that I can be a tester of this ? Just to > > test another OS. I imagine most of you use mac.... > > The Exupery VMs have closures. You can use them on both Windows and > Linux. I released them here to help people test the image without > needing to compile their own VMs. > Ok, so, I didn't understood what you said: "P.S. Don't use Exupery in a closure image, that'll probably crash. The issue is both Exupery and closures use the "unused" slot in MethodContext. I'll update Exupery to work with closure images as part of the next release." > > Bryce > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 31, 2009

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

by Michael Roberts

guys I have done a quick test of the closure image, with the mac VM on the inria page. I think it is probably unrelated but the old debugger in the core image is severely broken. Could someone please remind me 1) what we were going to do with the old debugger. I know there is work going on in the dev image on the new one... what is the strategy? 2) i'd appreciate if someone could see if there is a bug report that confirms this behaviour below. Otherwise I will at least file a report. Candidate bug report is #329 but I am not sure exactly if it is what I see. steps 1. run ClosureTests in the test runner 2. 3 fail, so click on testToDoWithArgument 3. hit debug 4. restart the test method 5. step over the to:do:. you only enter the loop block once, BUG #1 ? 6. step into the assertValues: method as it is highlighted 7. highlight now enters the loop again, not into the utility method. BUG #2 ? 8. carefully step until you get into the assert method, if you do this wrong a new notifier pops up BUG #3. if you kill this you get error unwind pop up that you can't ever kill. BUG #4 ? basically this debugger is unusable and I think it has been for some time. I'm sure I commented in the past. so please give me your thoughts on the old debugger and live issues in the tracker. Do people not notice, because they generally load the OB debugger? I want to know where to concentrate my efforts. I'm not sure we should develop the old debugger too much, but at one point it did work in squeak. I'm sure the unwind notifier bug predates pharo. surely it's not just me. my vote would be to attempt to fix the debugger, so we have one in the core image that works, and then perhaps leave it alone.. or we promote the new one into it when it can be a replacement. on the closure related note, what is perhaps interesting in a workspace is values := (1 to: 5) collect: [:each | [each] ]. values collect: [:each | each value] --> #(1 2 3 4 5) | i | values := (1 to: 5) collect: [:each | i := each. [i] ]. values collect: [:each | each value] -->#(5 5 5 5 5) values := OrderedCollection new. 1 to: 5 do: [:i | values add: [i] ]. values collect: [:each | each value] --> an OrderedCollection(6 6 6 6 6) I know the second and third gives non closure related result, but I don't know if the first one shows valid closure or not. Anyway please direct and I will keep testing. thanks, Mike

March 31, 2009

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

by Bryce Kampjes

On Tue, 2009-03-31 at 18:42 -0100, Mariano Martinez Peck wrote: > > Ok. Thanks. But, now I wonder, is there a linux and windows vm > somehere with closure so that I can be a tester of this ? Just to > test another OS. I imagine most of you use mac.... The Exupery VMs have closures. You can use them on both Windows and Linux. I released them here to help people test the image without needing to compile their own VMs. Bryce

March 31, 2009

[Pharo-project] cleaning some block arg assignemt :)

by StÃ©phane Ducasse

now we can recompile them :) Stef

March 31, 2009

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

by Mariano Martinez Peck

On Tue, Mar 31, 2009 at 6:35 PM, Bryce Kampjes <bryce(a)kampjes.demon.co.uk>wrote: > On Tue, 2009-03-31 at 15:30 +0200, Damien Cassou wrote: > > 2009/3/31 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > And in windows? I can also test it. the last windows exupery vm also > has > > > closure support ? > > > > I think so > > They are. Both the Linux and Windows Exupery VMs have the closure > bytecodes compiled in. They're both build from identical VMMaker > sources. > > Bryce > > P.S. Don't use Exupery in a closure image, that'll probably crash. The > issue is both Exupery and closures use the "unused" slot in > MethodContext. I'll update Exupery to work with closure images as part > of the next release. > Ok. Thanks. But, now I wonder, is there a linux and windows vm somehere with closure so that I can be a tester of this ? Just to test another OS. I imagine most of you use mac.... thanks Mariano > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 31, 2009