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

Re: [Pharo-project] Memory usage

by David T. Lewis

On Mon, Jul 23, 2012 at 09:26:18AM +0200, jannik.laval wrote: > Dear pharoers, > > We are loading really big models in the Moose software analysis platform. > This generate a lot of small objects and with the biggest model, we approach the limit of 2Gb of the VM. > > Is it possible for anyone who knows the VM to add extra memory space ? Going to 4Gb or maybe 8Gb would be a great thing. > It is possible to have an image of at least 7GB (I have done this on my PC with 8GB real memory). Currently this requires tracing the image to a 64-bit object format with SystemTracer, and running the image on an interpreter VM compiled for the 64-bit format. I expect that this will work for Moose in a Pharo image, although performance of the garbage collector is likely to become an issue as the memory grows with lots of smaller objects, and the 64-bit interpreter VM will be significantly slower than a 32-bit Cog VM. If you want to try this with one of your images, I'll try to give you some help. I believe that Eliot has longer term plans for 64-bit object formats, VMs, and improved garbage collectors. Dave

July 23, 2012

[Pharo-project] How to filter out method extensions in Ring?

by HernÃ¡n Morales Durand

Hello all, You may help me on this one. I want to filter out method selectors which are extensions of a particular class. For example, in Pharo 1.4 the ArrayedCollection class has these selectors: ArrayedCollection selectors asSortedCollection I would want all of them except #writeOnGZIPByteStream: which is in "Compression" package. I did a try to Ring ArrayedCollection selectors asSortedCollection collect: [ : each | RGMethodDefinition class: ArrayedCollection selector: each ] with MethodReference I did : ... ( each category beginsWith: '*' ) not ... but it seems not supported in Ring? Any hints? Cheers, HernÃ¡n

July 23, 2012

Re: [Pharo-project] Cairo, VM?

by Igor Stasenko

On 9 July 2012 14:31, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: > I need to adjust the path to the Cairo lib. > Some cleaning seems to be needed as nbLibraryNameOrHandle is redefined > several time. Or do I misunderstand something with the Trait ? > This trait used by multiple classes. Should be everything ok.. but i will check > Hilaire > > > > > > > On 07/07/2012 21:53, Igor Stasenko wrote: >> On 7 July 2012 21:44, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: >>> And for the Linux VM? >>> All are good? >>> >> linux NBCog should work just fine. >> >>> >>> Thanks >>> >>> Hilaire >>> >>> On 07/07/2012 06:26, Igor Stasenko wrote: >>>> RIght now for macs only.. >>>> https://ci.lille.inria.fr/pharo/view/NativeBoost/job/NB-Cog-Mac-Cocoa/29/ >>>> >>>> (well, actually linux one is *ready* too , you just need to install >>>> cairo library by yourself, >>>> and even, AFAIK, it is there by default in many linux distros >>>> >>>> on linux we don't need to care about bundling. >>>> >>> >>> >>> -- >>> Dr. Geo -- http://www.drgeo.eu >>> >>> >>> >>> >> >> >> > > > -- > Dr. Geo -- http://www.drgeo.eu > > > > -- Best regards, Igor Stasenko.

July 23, 2012

Re: [Pharo-project] athens for strikefonts

by Tudor Girba

Sure. I was just pinging to make sure the point does not get lost :) Cheers, Doru On Mon, Jul 23, 2012 at 1:26 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hi, Tudor & all. > > Yes. i will work on that in closest days.. > but first i need to finish with the VM update/upgrade cycle, so we > could have a better prepared VMs for Athens, SSL on Windows. > > On 22 July 2012 22:04, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Ah okay. I understand now >> >> Alexandre >> >> >> On Jul 22, 2012, at 11:50 AM, Tudor Girba wrote: >> >>> For the time being, StrikeFonts are the default fonts in Pharo. Given that it is the default it is used in practice all the time, and thus if we want Athens to be adopted easily we need support for the default case. >>> >>> The other solution is to change the default fonts, but this implies that we need to rethink how we distribute it, too, and I guess this will take a while. >>> >>> Cheers, >>> Doru >>> >>> >>> On 22 Jul 2012, at 16:40, Alexandre Bergel wrote: >>> >>>> Hi Doru, >>>> >>>> I am missing why StrikeFonts is so important for Moose. Is it the font used in all other the system? >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> >>>> On Jul 22, 2012, at 5:00 AM, Tudor Girba wrote: >>>> >>>>> Hi Igor, >>>>> >>>>> First of all, how was your holidays? :) >>>>> >>>>> A while ago, you said that supporting StrikeFonts would not be that difficult. For me it would be important to have this support in order to have a smooth transition to Athens even without Cairo. >>>>> >>>>> So, what would it take for this support to happen? >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> >>>>> On 11 Jul 2012, at 09:04, Tudor Girba wrote: >>>>> >>>>>> Aha. Ok. I will wait. >>>>>> >>>>>> Doru >>>>>> >>>>>> >>>>>> On Wed, Jul 11, 2012 at 8:43 AM, StÃ©phane Ducasse >>>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>>> Good idea if possible. >>>>>>> Igor like me is on vacation until 19 of july. >>>>>>> >>>>>>> On Jul 10, 2012, at 7:07 AM, Tudor Girba wrote: >>>>>>> >>>>>>>> Hi Igor, >>>>>>>> >>>>>>>> I just wanted to ask: is the little fix of having Athens work with StrikeFont still on the roadmap :)? >>>>>>>> >>>>>>>> As I mentioned before, this would make the adoption easier, because we can switch the Athens even with the regular CogVMs. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Doru >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> www.tudorgirba.com >>>>>>>> >>>>>>>> "It's not what we do that matters most, it's how we do it." >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> www.tudorgirba.com >>>>>> >>>>>> "Every thing has its own flow" >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "In a world where everything is moving ever faster, >>>>> one might have better chances to win by moving slower." >>>>> >>>>> >>>>> >>>>> >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Every now and then stop and ask yourself if the war you're fighting is the right one." >>> >>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > > > -- > Best regards, > Igor Stasenko. > -- www.tudorgirba.com "Every thing has its own flow"

July 23, 2012

Re: [Pharo-project] athens for strikefonts

by Igor Stasenko

Hi, Tudor & all. Yes. i will work on that in closest days.. but first i need to finish with the VM update/upgrade cycle, so we could have a better prepared VMs for Athens, SSL on Windows. On 22 July 2012 22:04, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Ah okay. I understand now > > Alexandre > > > On Jul 22, 2012, at 11:50 AM, Tudor Girba wrote: > >> For the time being, StrikeFonts are the default fonts in Pharo. Given that it is the default it is used in practice all the time, and thus if we want Athens to be adopted easily we need support for the default case. >> >> The other solution is to change the default fonts, but this implies that we need to rethink how we distribute it, too, and I guess this will take a while. >> >> Cheers, >> Doru >> >> >> On 22 Jul 2012, at 16:40, Alexandre Bergel wrote: >> >>> Hi Doru, >>> >>> I am missing why StrikeFonts is so important for Moose. Is it the font used in all other the system? >>> >>> Cheers, >>> Alexandre >>> >>> >>> On Jul 22, 2012, at 5:00 AM, Tudor Girba wrote: >>> >>>> Hi Igor, >>>> >>>> First of all, how was your holidays? :) >>>> >>>> A while ago, you said that supporting StrikeFonts would not be that difficult. For me it would be important to have this support in order to have a smooth transition to Athens even without Cairo. >>>> >>>> So, what would it take for this support to happen? >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 11 Jul 2012, at 09:04, Tudor Girba wrote: >>>> >>>>> Aha. Ok. I will wait. >>>>> >>>>> Doru >>>>> >>>>> >>>>> On Wed, Jul 11, 2012 at 8:43 AM, StÃ©phane Ducasse >>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>> Good idea if possible. >>>>>> Igor like me is on vacation until 19 of july. >>>>>> >>>>>> On Jul 10, 2012, at 7:07 AM, Tudor Girba wrote: >>>>>> >>>>>>> Hi Igor, >>>>>>> >>>>>>> I just wanted to ask: is the little fix of having Athens work with StrikeFont still on the roadmap :)? >>>>>>> >>>>>>> As I mentioned before, this would make the adoption easier, because we can switch the Athens even with the regular CogVMs. >>>>>>> >>>>>>> Cheers, >>>>>>> Doru >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> www.tudorgirba.com >>>>>>> >>>>>>> "It's not what we do that matters most, it's how we do it." >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "Every thing has its own flow" >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "In a world where everything is moving ever faster, >>>> one might have better chances to win by moving slower." >>>> >>>> >>>> >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Every now and then stop and ask yourself if the war you're fighting is the right one." >> >> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- Best regards, Igor Stasenko.

July 23, 2012

Re: [Pharo-project] dirty package

by Marcus Denker

On Jul 23, 2012, at 12:17 PM, Pavel Krivanek wrote: > Hi, > > in the image 20231 on Jenkins there is a dirty package KernelTests. this is fixed in 20232... we really need to get jenkins again to automatically update. -- Marcus Denker -- http://marcusdenker.de

July 23, 2012

[Pharo-project] Who wants to do a Spec/Zinc/Fuel experiment? [WAS] Re: fuelized test failures

by Mariano Martinez Peck

On Fri, Jul 20, 2012 at 6:09 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > From now on all the test-failures are serialized on the build server. > > This allows us to quickly find the cause of a failing test: > - download the .fuel file for the failing test > - materialize the .fuel in the image and debug the code > | aContext | > aContext := FLMaterializer materializeFromFileNamed: > 'PharoDebug.fuel'. > Debugger openContext: aContext label: 'This is the new debugger!' > contents: nil > > The serialized stack trace is very limited (generally only 2 contexts) but > they > are enough to get a decent view on what the variables are > I was thinking....it should be really easy to build a very simple UI that: - lets you select/write a Jenkins job and a test - downloads the .fuel - materialize it and open the debugger Anyone interested? Ben do you need another tool for your paper/chapter? ;) Cheers, -- Mariano http://marianopeck.wordpress.com

July 23, 2012

[Pharo-project] dirty package

by Pavel Krivanek

Hi, in the image 20231 on Jenkins there is a dirty package KernelTests. -- Pavel

July 23, 2012

Re: [Pharo-project] fuelized test failures

by Mariano Martinez Peck

On Sun, Jul 22, 2012 at 11:11 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Jul 22, 2012, at 10:00 AM, StÃ©phane Ducasse wrote: > > > I love that scenario :) > > This is great that powerful tools let us imagine and build solutions > that would not be possible > > before. Power to imaginationâ¦ > > > And it is an example for a building block that helps to build things. > Things that are *impossible* > without it. > > Another way to view Fuel is that of a scientific experiment: We > empirically study the existing > (ImageSegment). Without pre-concived notions to replace it! (We actually > thought ImageSegments > would turn out to be the greatest thing ever and just needed some > documentation/more understandable > implementation). > Indeed. I remember my first months in Douai for my PhD making drawings to understand the IS primitives :) And then Martin arrived hahaha. > -> You study the existing > -> You claim that you can do better > -> You do better. > > And then the next step is *extremeley* importnat: > > -> You prove that it is better for real by *replacing* ALL the existing > subsystems that do the same. > > That last part is very essential: in the end, you often see that it is > actually not that easy. > That's a real good point. In Spanish I would say "Los pingos se ven en la cancha" > > So *replacing* is important. The other thing important is to realize that > it enables things that are impossible > without. > > +1 Fuel is getting more and more users. Even in BioInformatics: http://biosmalltalk.blogspot.fr/2012/07/custom-serialization-of-big-dna-or.… http://rmod.lille.inria.fr/web/pier/software/Fuel/Software-using-Fuel Cheers, -- Mariano http://marianopeck.wordpress.com

July 23, 2012

Re: [Pharo-project] Problem/ommission in Pharo 2.0?

by Guillermo Polito

The #default method was renamed to #uniqueInstance. The issue already has been forwarded to Dale to see how we can make metacello load again. Cheers, Guille On Mon, Jul 23, 2012 at 11:44 AM, Friedrich Dominicus < frido(a)q-software-solutions.de> wrote: > I don't know if that really is a problem. Hoewever > in MCCacheRepository there is the default class side message missing. > This is needed to load I guess any Metacello package. > > Regards > Friedrich > >

July 23, 2012