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

Re: [Pharo-project] To the finish line! (please review an issue)

by Sean P. DeNigris

StÃ©phane Ducasse wrote > Sean this is a bit chaotic for me here. We have a community of skilled, generous people. You don't need to do it all yourself ;) -- View this message in context: http://forum.world.st/To-the-finish-line-please-review-an-issue-tp4667841p4… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 5, 2013

Re: [Pharo-project] [ANN] NativeBoost project moved to new hosting: smalltalkhub

by Igor Stasenko

On 5 February 2013 22:44, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-02-05, at 22:35, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> hmm >> wget --quiet -qO - >> http://pharo.gforge.inria.fr/ci/script/ciPharo20NBCogVM.sh | bash >> >> don't seems to work for me on windows: >> >> bash ciPharo20NBCogVM.sh >> --2013-02-05 22:33:39-- >> http://pharo.gforge.inria.fr/ci/vm/nbcog/Windows_NT/nbcog-Windows_NT-latest… >> Resolving pharo.gforge.inria.fr... 131.254.249.53 >> Connecting to pharo.gforge.inria.fr|131.254.249.53|:80... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2013-02-05 22:33:39 ERROR 404: Not Found. > > wrong environment variable for $OS? > > on jenkins we manually set the env var I think.. yes. but it is set on mingw shell: echo $OS Windows_NT i suppose it will work if i set it to 'win'. but then i think it may break other stuff which depends on it.. perhaps we should use less conflicting variable name (like 'JENKINS_OS'), and if it is not set, then detect OS via uname.. etc (sounds like we will need another crappy bash script with a lot of if statements) . because then it kind of defeats the idea of having zero-conf scripts. -- Best regards, Igor Stasenko.

Feb. 5, 2013

Re: [Pharo-project] [ANN] NativeBoost project moved to new hosting: smalltalkhub

by Camillo Bruni

On 2013-02-05, at 22:35, Igor Stasenko <siguctua(a)gmail.com> wrote: > hmm > wget --quiet -qO - > http://pharo.gforge.inria.fr/ci/script/ciPharo20NBCogVM.sh | bash > > don't seems to work for me on windows: > > bash ciPharo20NBCogVM.sh > --2013-02-05 22:33:39-- > http://pharo.gforge.inria.fr/ci/vm/nbcog/Windows_NT/nbcog-Windows_NT-latest… > Resolving pharo.gforge.inria.fr... 131.254.249.53 > Connecting to pharo.gforge.inria.fr|131.254.249.53|:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 2013-02-05 22:33:39 ERROR 404: Not Found. wrong environment variable for $OS? on jenkins we manually set the env var I think..

Feb. 5, 2013

Re: [Pharo-project] pharo VM names

by Esteban Lorenzano

No, I disagree... expose as names elements of the architecture is a bad choice. bad marketing to choose ugly names, just for the sake of our techie guys (my self included :P) the unique official VM for pharo will be called Pharo, and it will be a Cog VM with our additions. we also will provide another supplementary VM (the StackVM, with a suffix, to accomplish 2 thins: make clear that is not the official, and provide information about why is there). It will be there because is more portable and more stable (for now, we hope to have same stability with the cog soon). We don't need two suffixes, just one, because the official vm is just one. Esteban On Tue, Feb 5, 2013 at 10:26 PM, Esteban A. Maringolo <emaringolo(a)gmail.com>wrote: > I there is going to be a suffix for the VM, I would name them PharoJIT > and PharoStack. So both have suffixes, otherwise Pharo"S" sounds like > it has something else the "clean" Pharo doesn't. > > Just my view on naming things. > > Regards, > > Esteban A. Maringolo > > > 2013/2/5 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > Camillo > > > > the stackVM can be important as a fallback > > So we can have Pharo and PharoS (as slow and stack) > >

Feb. 5, 2013

Re: [Pharo-project] [ANN] NativeBoost project moved to new hosting: smalltalkhub

by Igor Stasenko

hmm wget --quiet -qO - http://pharo.gforge.inria.fr/ci/script/ciPharo20NBCogVM.sh | bash don't seems to work for me on windows: bash ciPharo20NBCogVM.sh --2013-02-05 22:33:39-- http://pharo.gforge.inria.fr/ci/vm/nbcog/Windows_NT/nbcog-Windows_NT-latest… Resolving pharo.gforge.inria.fr... 131.254.249.53 Connecting to pharo.gforge.inria.fr|131.254.249.53|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2013-02-05 22:33:39 ERROR 404: Not Found. -- Best regards, Igor Stasenko.

Feb. 5, 2013

Re: [Pharo-project] pharo VM names

by Eliot Miranda

On Tue, Feb 5, 2013 at 1:21 PM, Camillo Bruni <camillobruni(a)gmail.com>wrote: > > On 2013-02-05, at 22:15, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > On Tue, Feb 5, 2013 at 1:12 PM, Camillo Bruni <camillobruni(a)gmail.com > >wrote: > > > >> done: > >> https://ci.inria.fr/pharo/view/VM/job/StackVM/ > >> https://ci.inria.fr/pharo/view/VM/job/PharoVM/ > > > > > > "The Pharo VM (former Cog VM) is a VM that optimizes execution by mapping > > contexts to stack frames and lazily instantiating contexts. > > It further jits/compiles methods used more than once to machine-code and > > implements a number of send optimization schemes in that machine-code." > > => > > "The Pharo VM (also known as the Cog VM) is a VM that optimizes execution > > by mapping contexts to stack frames and lazily instantiating contexts. > > It further jits/compiles methods used more than once to machine-code and > > implements a number of send optimization schemes in that machine-code." > > nope it is NOT the cog VM, your branch doesn't have a set of changes we > made, > notably to the file plugins, furthermore we ship by default with the native > boost plugin. > > so to be fully correct I have to say *former*. > No. Cog is an architecture, a JIT plus an Interpreter, not a specific VM. StackVM is an architecture. Interpreter VM is an architecture. You could clarify by saying "The Pharo VM (a derivative of the Cog VM) ..." or "The Pharo VM (a version of the Cog VM) ..." -- best, Eliot

Feb. 5, 2013

Re: [Pharo-project] To the finish line! (please review an issue)

by StÃ©phane Ducasse

On Feb 5, 2013, at 10:23 PM, Camillo Bruni wrote: > > On 2013-02-05, at 22:21, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> >> On Feb 5, 2013, at 10:14 PM, Camillo Bruni wrote: >> >>> thanks! I love to see somebody else than marcus/esteban >> and stef :) > > *blush* right :D I take it easy (and you know I can be really mad/sad for certain stuff related to ack ;D)

Feb. 5, 2013

Re: [Pharo-project] pharo VM names

by Esteban A. Maringolo

I there is going to be a suffix for the VM, I would name them PharoJIT and PharoStack. So both have suffixes, otherwise Pharo"S" sounds like it has something else the "clean" Pharo doesn't. Just my view on naming things. Regards, Esteban A. Maringolo 2013/2/5 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Camillo > > the stackVM can be important as a fallback > So we can have Pharo and PharoS (as slow and stack)

Feb. 5, 2013

Re: [Pharo-project] [ANN] NativeBoost project moved to new hosting: smalltalkhub

by StÃ©phane Ducasse

>>> Camillo >>> >>> I want to write one little but utterly important chapter for the book: >>> Pharo Zero Config. >>> >>> I want to sit with me and you show me what I missed and the command line stuff >>> and I write that three/five page essential chapter. >> >> ok I am definitely in for that! > > can i join? because i am almost completely ignorant of this stuff. may be :) I should be free from 10h so :) >>> tomorrow I want to sit with clement around mate and that! >> >> nice! > > > > -- > Best regards, > Igor Stasenko. >

Feb. 5, 2013

Re: [Pharo-project] pharo VM names

by Camillo Bruni

On 2013-02-05, at 22:23, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Camillo > > the stackVM can be important as a fallback > So we can have Pharo and PharoS (as slow and stack) I agree, maybe we could merge that with the Rizel code? so we only need 2 VMs?

Feb. 5, 2013