February 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Proposal: coverage tests

by Pavel Krivanek

Hi, what about to intrroduce tests that will test coverage of tests? Some improved version of the code below. Are there some tool for Smalltalk showing uncovered lines of code? There are such tools in Java world :-) One little problem is that this code do not work on Linux because of a VM error that cause test failures on CI server too. Cheers, Pavel | class test trace classTrace result | class := Time. test := TimeTest. trace := Dictionary new. thisContext runSimulated: [test suite run] contextAtEachStep: [ :current | | cls sel methods bytecodes | cls := current method methodClass. sel := current method selector. methods := trace at: cls ifAbsentPut: Dictionary new. bytecodes := methods at: sel ifAbsentPut: Set new. bytecodes add: current pc.] trace . result := String streamContents: [:s | classTrace := trace at: class ifAbsent: nil. classTrace ifNil: [ s nextPutAll: 'Class ', class name, ' not called'; cr. ] ifNotNil: [ s nextPutAll: class name; cr. class selectorsDo: [:sel | | m usedBytecodes allBytecodes | m := class >> sel. usedBytecodes := (classTrace at: sel ifAbsent: Set new) size. allBytecodes := 0. m symbolicLinesDo: [:pc :lineForPC | allBytecodes := allBytecodes + 1 ].. s tab; nextPutAll: sel; nextPutAll: ' - '; nextPutAll: (usedBytecodes / allBytecodes * 100) asFloat asString; nextPutAll: '%'; cr. ]]. ]. result..

Feb. 21, 2012

Re: [Pharo-project] Netstyle experience

by Sven Van Caekenberghe

Hi Dave, On 21 Feb 2012, at 15:34, Dave Mason wrote: > This is the biggest thing for me. I'm trying to get my Analysis of Algorithms students to recognise and value a powerful environment like Pharo Smalltalk, but some of them are experiencing so many crashes that they've taken to entering their code in Notepad and then pasting it into Pharo!!! This is not a strong advert for Smalltalk or Pharo. > > I suspect many of these crashes are stack overflows. I *thought* that Squeak/Pharo was supposed to recognise stack overflow, but I just wrote a method: > crash > ^self crash + 4 > and my image grew to 500+MB and then crashed. This is with Pharo 1.3 one-click. With 1.1 one-click, I *do* get the Low space window popping up at 516MB (although I don't appear able to do much... it doesn't even seem to quit-no-save); I eventually did a force-quit. This is all on Mac OS X 10.6.8. > The 1.3 says: > VM: Mac OS - intel - 1068 - Croquet Closure Cog VM > [CoInterpreter VMMaker-oscog- IgorStasenko.123] 21.0 > Image: Pharo1.3 [Latest update: #13307] > > How can I get more stability? Is it time to move to 1.4? Is there something I or my students can do to help? > > Thanks for everybody's efforts! > > ../Dave Out of the box experience is indeed very important. There was an important fix related to stopping infinite loops recently, I am sure the latest 1.4 includes it. Sven

Feb. 21, 2012

[Pharo-project] [update 1.4] #14345

by Marcus Denker

14345 ----- Issue 5343: Debugger broken http://code.google.com/p/pharo/issues/detail?id=5343 Issue 5342: Do not unload Graphics Ressources on #cleanUpForProduction http://code.google.com/p/pharo/issues/detail?id=5342 -- Marcus Denker -- http://marcusdenker.de

Feb. 21, 2012

Re: [Pharo-project] Pharo VM

by Pavel Krivanek

I'm asking because Stef mentioned that and I told it to a friend that should create and maintain Fedora packages for Pharo. So he naturally decided to wait.... Cheers, -- Pavel On Tue, Feb 21, 2012 at 3:31 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > well.. we already have git repositories: > > https://gitorious.org/cogvm/blessed > > and a cool process to build vm's: > > http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-us… > http://marianopeck.wordpress.com/2011/04/16/building-the-vm-second-part/ > > and I'm even packaging "pharo branded vm's" for mac: > > https://ci.lille.inria.fr/pharo/view/VM/job/Pharo-Mac-Cocoa/ > > but this last part is just a "start job"... more need to be done. > to be clear: we are NOT forking cog or anything, just branding it in a way > who fit us better, and working on plugins we think are needed to be there. > > best, > Esteban > > El 21/02/2012, a las 9:58a.m., Schwab,Wilhelm K escribiÃ³: > > And when do we begin to "live long and prosper" with Spock's help? Â Â Sorry, > had to ask, it's a wonderful idea. > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr > [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Pavel Krivanek > [pavel.krivanek(a)gmail.com] > Sent: Tuesday, February 21, 2012 7:10 AM > To: Pharo Development > Subject: [Pharo-project] Pharo VM > > Hi Stef, > > last year you mentioned that in January you want to brand our own VM. > Is there any progress in this area? Will there be still two VMs (Cog > and Stack)? Will we have own git repository? > > Cheers, > -- Pavel > > >

Feb. 21, 2012

Re: [Pharo-project] Netstyle experience (was Do not feed the trolls)

by Camillo Bruni

yeah I agree that would be great if a debugger would popup there... On 2012-02-21, at 15:34, Dave Mason wrote: > > On Feb 21, 2012, at 07:07, Janko MivÅ¡ek wrote: > >> - more stability, > > This is the biggest thing for me. I'm trying to get my Analysis of Algorithms students to recognise and value a powerful environment like Pharo Smalltalk, but some of them are experiencing so many crashes that they've taken to entering their code in Notepad and then pasting it into Pharo!!! This is not a strong advert for Smalltalk or Pharo. > > I suspect many of these crashes are stack overflows. I *thought* that Squeak/Pharo was supposed to recognise stack overflow, but I just wrote a method: > crash > ^self crash + 4 > and my image grew to 500+MB and then crashed. This is with Pharo 1.3 one-click. With 1.1 one-click, I *do* get the Low space window popping up at 516MB (although I don't appear able to do much... it doesn't even seem to quit-no-save); I eventually did a force-quit. This is all on Mac OS X 10.6.8. > The 1.3 says: > VM: Mac OS - intel - 1068 - Croquet Closure Cog VM > [CoInterpreter VMMaker-oscog- IgorStasenko.123] 21.0 > Image: Pharo1.3 [Latest update: #13307] > > How can I get more stability? Is it time to move to 1.4? Is there something I or my students can do to help? > > Thanks for everybody's efforts! > > ../Dave

Feb. 21, 2012

Re: [Pharo-project] Netstyle experience (was Do not feed the trolls)

by Dave Mason

On Feb 21, 2012, at 07:07, Janko MivÅ¡ek wrote: > - more stability, This is the biggest thing for me. I'm trying to get my Analysis of Algorithms students to recognise and value a powerful environment like Pharo Smalltalk, but some of them are experiencing so many crashes that they've taken to entering their code in Notepad and then pasting it into Pharo!!! This is not a strong advert for Smalltalk or Pharo. I suspect many of these crashes are stack overflows. I *thought* that Squeak/Pharo was supposed to recognise stack overflow, but I just wrote a method: crash ^self crash + 4 and my image grew to 500+MB and then crashed. This is with Pharo 1.3 one-click. With 1.1 one-click, I *do* get the Low space window popping up at 516MB (although I don't appear able to do much... it doesn't even seem to quit-no-save); I eventually did a force-quit. This is all on Mac OS X 10.6.8. The 1.3 says: VM: Mac OS - intel - 1068 - Croquet Closure Cog VM [CoInterpreter VMMaker-oscog- IgorStasenko.123] 21.0 Image: Pharo1.3 [Latest update: #13307] How can I get more stability? Is it time to move to 1.4? Is there something I or my students can do to help? Thanks for everybody's efforts! ../Dave

Feb. 21, 2012

Re: [Pharo-project] Pharo VM

by Esteban Lorenzano

Hi, well.. we already have git repositories: https://gitorious.org/cogvm/blessed and a cool process to build vm's: http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-us… http://marianopeck.wordpress.com/2011/04/16/building-the-vm-second-part/ and I'm even packaging "pharo branded vm's" for mac: https://ci.lille.inria.fr/pharo/view/VM/job/Pharo-Mac-Cocoa/ but this last part is just a "start job"... more need to be done. to be clear: we are NOT forking cog or anything, just branding it in a way who fit us better, and working on plugins we think are needed to be there. best, Esteban El 21/02/2012, a las 9:58a.m., Schwab,Wilhelm K escribiÃ³: > And when do we begin to "live long and prosper" with Spock's help? Sorry, had to ask, it's a wonderful idea. > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Pavel Krivanek [pavel.krivanek(a)gmail.com] > Sent: Tuesday, February 21, 2012 7:10 AM > To: Pharo Development > Subject: [Pharo-project] Pharo VM > > Hi Stef, > > last year you mentioned that in January you want to brand our own VM. > Is there any progress in this area? Will there be still two VMs (Cog > and Stack)? Will we have own git repository? > > Cheers, > -- Pavel > >

Feb. 21, 2012

Re: [Pharo-project] Why do we use Pharo? a.k.a. rethinking Pharo marketing

by Esteban Lorenzano

Pharo: enterprise applications at prototype speed :) (I'm one of the guys who hear "enterprise" and get scared, but thats probably because of my java-past :() best, Esteban El 21/02/2012, a las 9:08a.m., Sven Van Caekenberghe escribiÃ³: > > On 21 Feb 2012, at 09:52, GÃ¶ran Krampe wrote: > >> Pharo (or Smalltalk in general) is for me about *speed* of development. >> >> Yes, one can make a huge list of other attributes - but it all boils down to that *for me*. For example, one could say "no, it is also about quality of code through good OO design" - but if you think about it, quality of design gives *speed*. The quality in itself doesn't give me "value" (well, I am being black-and-white here), but the speed that a good quality codebase gives me (in adapting to change etc) is true hard value. That speed makes programming fun. That speed impresses people. That speed is a true distinguishing feature. >> >> And of course, the speed comes as a product of many factors of which some are unique (but not all of them are): >> >> language-brevity * language-modeling-capability * tools * dynamic-typing * instant-compilation * app-always-running = awesome speed! >> >> ...and if we break out tools from the above equation: >> >> tools = full-reflection * written-all-in-itself * everyone-can-contribute-no-need-for-plugin-system-like-eclipse * crossplatform-so-everyone-can-contribute-regardless-of-OS >> >> >> So if I would "pitch" Pharo to other developers, it would be about the extravagant speed of development. Sure, cross platform and good performance through Cog is nice, but for me and many other web devs (which perhaps contitutes 90% of the audience) it would be Linux anyway and the VM speed is not a real problem. But as I said, cross-platform is important for us to be able to work together on "common ground" improving the environment. > > Yes, well written and so true (for me in any case). > > Once you are used to Smalltalk it is so hard to go back, it is hard to describe. > > Thx, > > Sven

Feb. 21, 2012

[Pharo-project] [update 1.4] #14344

by Marcus Denker

14344 ----- Issue 5341: update #cleanUpForProduction http://code.google.com/p/pharo/issues/detail?id=5341 -- Marcus Denker -- http://marcusdenker.de

Feb. 21, 2012

Re: [Pharo-project] Why do we use Pharo? a.k.a. rethinking Pharo marketing

by Stephan Eggermont

We use Pharo commercially because it offers us a number of critical competitive advantages: - the superior environment makes development fun; - the short development feedback loop allows us to learn and improve; - open source & cross-platform allow us to make deployment decisions purely on technical reasons; - the talent in the community gives us the guarantee that we can buy our way to a solution if needed; the focus on both research and commerce makes sure that there are good people that continue improving Pharo and that they can stay in the Pharo community after graduating; - the availability of frameworks such as MOOSE and Seaside and the good compatibility with Gemstone allows us to provide better solutions faster. Stephan Eggermont Sensus, systems that make sense

Feb. 21, 2012