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

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

by Camillo Bruni

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

Feb. 5, 2013

Re: [Pharo-project] pharo VM names

by StÃ©phane Ducasse

Camillo the stackVM can be important as a fallback So we can have Pharo and PharoS (as slow and stack) On Feb 5, 2013, at 4:34 PM, Camillo Bruni wrote: > > On 2013-02-05, at 16:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> Hi, >> >> 1) CI builds names is not the same than app names. > > I am talking about the artifact names if that wasn't clear. > >> 2) The "official" pharo vm (the NB Cog JIT), should be named just "Pharo", because that is what users will see in his dock bar. >> 3) The stack VM is not a debug vm is just a VM who uses a stack-to-register approach. I would call it PharoS or something that simple. > > think about the user perspective? why would I even bother taking this VM? > There is one that is fast, and another one that is what? less stable? > > >> 4) RizelVM is not a regularly distributed VM, so it should not be in pharo, but in pharo-contribution > yes, definitely. > >> 5) PLEASE, STOP MARKING ISSUES THAT CAN WAIT AS 2.0!!!! We are just 2 weeks of release. Stop adding new tasks. No matter if you think is important. Unless it will block us to release, IT IS NOT. > > I associated this with Pharo2.0 ... I guess wrongly.. > > I provide fixes that can be included NOW => I have to mark them 2.0 otherwise nobody will ever ever look at it. > => did you ever touch the monkey? You didn't, so unless that is fixed and it checks 3.0 tags as well, I can't help myself but putting it on 2.0

Feb. 5, 2013

Re: [Pharo-project] pharo VM names

by Camillo Bruni

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*.

Feb. 5, 2013

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

by StÃ©phane Ducasse

On Feb 5, 2013, at 10:14 PM, Camillo Bruni wrote: > thanks! I love to see somebody else than marcus/esteban and stef :) Sean this is a bit chaotic for me here. Teaching + meeting when not :) But it will come. Stef > cleaning up the issues :P > > On 2013-02-05, at 21:58, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > >> I spent the day on the issue tracker... Out of the 56 2.0 issues remaining >> [1], 5 are ready to be integrated [2], and 17 are /so/ close and just need a >> review [3]. Many of [3] will be quick to review (e.g. make sure that the >> slice loads, evaluate a snippet from the issue comment). So if you find >> yourself waiting for a bus or stuck in an elevator for 10 minutes... ;) >> Let's burn through these and get to creating the next chapter of our >> future!!! >> >> [1] http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D2.0 >> [2] >> http://code.google.com/p/pharo/issues/list?can=2&q=status%3AFixToInclude+Mi… >> [3] >> http://code.google.com/p/pharo/issues/list?can=2&q=status%3AFixReviewNeeded… >> >> >> >> -- >> View this message in context: http://forum.world.st/To-the-finish-line-please-review-an-issue-tp4667841.h… >> 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 StÃ©phane Ducasse

On Feb 5, 2013, at 10:09 PM, Camillo Bruni wrote: > > On 2013-02-05, at 21:59, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Camillo >> >> you are favorite swiss. I love your burst of anger/rage! and I'm serious :) > > hahaha, well â I also should learn to contain myself, I do not want that my environment > acts in fear of my outbursts :( Yes I think that letting the steam out is also good. Getting calm should come with age. :) At least I'm much calmer I was used to be. > >>> And if you had a look at it you would maybe give me instructive comments? >>> Right now it reads as a global disagreement :/ with which I can only disagree >> >> yes I read it like that too. >> and you are right not having a place to get the pharo athens vm + athens loaded is a pain to push people to use it. > > > so yes, the question of documentation? > > => one part goes into the git repository (remember oscar's famous README.txt files? we should start with those...) > - I started a clean repos here: https://github.com/pharo-project/ci > > => the other part goes on the jenkins jobs (I guess you started documenting it in chile?) > - where does stuff come from > - where does it go to? > - and who is responsible? (I want a personal phone number on each job ;)

Feb. 5, 2013

Re: [Pharo-project] pharo VM names

by Esteban Lorenzano

yes, it is not "formerly known", it is just a branding for cog vm. Esteban On Tue, Feb 5, 2013 at 10:15 PM, 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." > > please. > > >> >> On 2013-02-05, at 22:09, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >> > doing that right now! >> > >> > On 2013-02-05, at 22:08, Francois Stephany <tulipe.moutarde(a)gmail.com> >> wrote: >> >> On 05/02/13 21:15, Eliot Miranda wrote: >> >> >> >>> >> >>> No. The StackVM is a VM that optimizes interpreted execution by >> mapping >> >>> contexts to stack frames and lazily instantiating contexts, but is >> still >> >>> a pure interpreter. The Cog VM is a VM that optimizes execution >> >>> by mapping contexts to stack frames and lazily instantiating contexts, >> >>> /and/ by compiling methods used more than once to machine-code and >> >>> implementing a number of send optimization schemes in that >> machine-code. >> >>> >> >> >> >> This could be added in the Jenkins job description! >> >> >> > >> >> >> > > > -- > best, > Eliot >

Feb. 5, 2013

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

by Igor Stasenko

On 5 February 2013 22:13, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > On 2013-02-05, at 22:08, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> 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. > >> 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 Eliot Miranda

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." please. > > On 2013-02-05, at 22:09, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > > doing that right now! > > > > On 2013-02-05, at 22:08, Francois Stephany <tulipe.moutarde(a)gmail.com> > wrote: > >> On 05/02/13 21:15, Eliot Miranda wrote: > >> > >>> > >>> No. The StackVM is a VM that optimizes interpreted execution by > mapping > >>> contexts to stack frames and lazily instantiating contexts, but is > still > >>> a pure interpreter. The Cog VM is a VM that optimizes execution > >>> by mapping contexts to stack frames and lazily instantiating contexts, > >>> /and/ by compiling methods used more than once to machine-code and > >>> implementing a number of send optimization schemes in that > machine-code. > >>> > >> > >> This could be added in the Jenkins job description! > >> > > > > > -- best, Eliot

Feb. 5, 2013

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

by Camillo Bruni

thanks! I love to see somebody else than marcus/esteban cleaning up the issues :P On 2013-02-05, at 21:58, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > I spent the day on the issue tracker... Out of the 56 2.0 issues remaining > [1], 5 are ready to be integrated [2], and 17 are /so/ close and just need a > review [3]. Many of [3] will be quick to review (e.g. make sure that the > slice loads, evaluate a snippet from the issue comment). So if you find > yourself waiting for a bus or stuck in an elevator for 10 minutes... ;) > Let's burn through these and get to creating the next chapter of our > future!!! > > [1] http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D2.0 > [2] > http://code.google.com/p/pharo/issues/list?can=2&q=status%3AFixToInclude+Mi… > [3] > http://code.google.com/p/pharo/issues/list?can=2&q=status%3AFixReviewNeeded… > > > > -- > View this message in context: http://forum.world.st/To-the-finish-line-please-review-an-issue-tp4667841.h… > 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 Camillo Bruni

On 2013-02-05, at 22:08, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > 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! > tomorrow I want to sit with clement around mate and that! nice!

Feb. 5, 2013