- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Pharo Consortium New Platinum Member: ENSTA Bretagne

by Stephane Ducasse

We are super happy! On Tue, Feb 13, 2018 at 7:55 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > The Pharo Consortium is very happy to announce that ENSTA Bretagne > has joined the Consortium as a Platinum Member. > > About > - ENSTA Bretagne: http://www.ensta-bretagne.fr > - Pharo Consortium: http://consortium.pharo.org > > The goal of the Pharo Consortium is to allow companies and institutions to > support the ongoing development and future of Pharo. > > Individuals can support Pharo via the Pharo Association: > > - http://association.pharo.org >

Feb. 13, 2018

Re: [Pharo-dev] Ficus question

by Stephane Ducasse

Thanks martin. I will check with Pavel when he is back from vacation because these traits looks dated to me. S. On Tue, Feb 13, 2018 at 7:58 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hi Stef, I've just loaded Ficus in latest 6.1, and I didn't find any usage > of TClass. > > I printed "TClass users" and got "an IdentitySet(Trait Class)" > > Then I browsed the code, and what I see in relation to your question is: > > - RFiBehavior uses TClassDescription and TBehavior > - RFiAbstractTrait uses TComposingDescription and > TTransformationCompatibility > > This is part of the FicusRing package. > > > FYI, I loaded the project the same way as the bootstrap may be loading the > code (is it loading it?): > > EpMonitor current disable. > Metacello new > smalltalkhubUser: 'MartinDias' project: 'Ficus'; > configuration: #Ficus; > version: #development; > load: #mini. > > > MartÃn > > On Tue, Feb 13, 2018 at 2:23 PM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: >> >> Hi martin >> >> I would like to know what is the API Ficus uses from TClass. >> Do you have an idea? >> >> >> Stef >> >

Feb. 13, 2018

Re: [Pharo-dev] Ficus question

by Martin Dias

Hi Stef, I've just loaded Ficus in latest 6.1, and I didn't find any usage of TClass. I printed "TClass users" and got "an IdentitySet(Trait Class)" Then I browsed the code, and what I see in relation to your question is: - RFiBehavior uses TClassDescription and TBehavior - RFiAbstractTrait uses TComposingDescription and TTransformationCompatibility This is part of the FicusRing package. FYI, I loaded the project the same way as the bootstrap may be loading the code (is it loading it?): EpMonitor current disable. Metacello new smalltalkhubUser: 'MartinDias' project: 'Ficus'; configuration: #Ficus; version: #development; load: #mini. MartÃn On Tue, Feb 13, 2018 at 2:23 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi martin > > I would like to know what is the API Ficus uses from TClass. > Do you have an idea? > > > Stef > >

Feb. 13, 2018

[ANN] Pharo Consortium New Platinum Member: ENSTA Bretagne

by Marcus Denker

The Pharo Consortium is very happy to announce that ENSTA Bretagne has joined the Consortium as a Platinum Member. About - ENSTA Bretagne: http://www.ensta-bretagne.fr - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: - http://association.pharo.org

Feb. 13, 2018

Ficus question

by Stephane Ducasse

Hi martin I would like to know what is the API Ficus uses from TClass. Do you have an idea? Stef

Feb. 13, 2018

Re: [Pharo-dev] OpalCompiler evaluate speed

by Marcus Denker

> On 24 Nov 2017, at 10:54, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 23 Nov 2017, at 23:37, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: >> >> Hi Nicolas. >> >> Just some comments: >> >> Another thing you can try is to remove the allocation of Opal's IR. It seems people use the IR only through the IRBuilder, so the API can be kept but it can generate directly bytecode instead of IR then bytecode. Removing those allocations would speed things up. It means merging IRFix / IRTranslator / IRBytecodeGenerator somehow and have the IRBuilder API directly call the new resulting merged class. >> >> Another thing is that when Opal became the default compiler, I evaluated the speed and saw it was slower, but when loading large projects it seemed loading time was dominated by Monticello / source reading / source loading and the compilation time was overall not that significant (< 20% of time). I don't know if this is still the case with GIT. I have problems currently when editing some large methods (it seems in the IDE the method is compiled at each keystroke...) and when doing OpalCompiler recompileAll (which I do often since I edit bytecode sets) but else the performance of Opal seems to be OK. Evaluate performance may be relevant in some cases but I've never found such cases outside of the IDE in production. >> > (old mailâ¦ late answer). In the meantime we found out that #recompileAll was recompiling meta-classes twice, with that fixed rempiling is a little bit faster (from around one minute to 50 seconds on my machine). > > One other thing that needs cleanup: the API/ OpalCompiler class. This tries to be compatible with the old API (e.g. failBlock) and got quite hacked to death over > timeâ¦ we should clean that up. The complexity of #evaluate is partly due to that, I think. > As a first step, I changed #evaluate to not store sources in the trailer, this means that we do not pretty-print the source anymore. https://github.com/pharo-project/pharo/pull/880 The only downside is that a (not very practically relevant) test failed (#testSourceNodeOptimizedBlock). I think we can ignore that for now and fix it when it turns out to be a problem (the test works fine when rewritten to compile a full method). Marcus

Feb. 13, 2018

Re: [Pharo-dev] Best VM for the Mac>

by Sean P. DeNigris

EstebanLM wrote > no because for some reason libgit2 was not in the final bundle for mac. > I need to check what happened there. Okay, I'll stand by. Thanks for the update. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Feb. 13, 2018

Re: [Pharo-dev] Best VM for the Mac>

by Esteban Lorenzano

no because for some reason libgit2 was not in the final bundle for mac. I need to check what happened there. Esteban > On 13 Feb 2018, at 14:55, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Stephane Ducasse-3 wrote >> Well, do NOT rely on them on Sierra. >> I can crash such VM while typing code. >>>>>>> wget -O- get.pharo.org/vmLatest70 | bash >>>>>>> wget -O- get.pharo.org/64/vmLatest70 | bash > > Are these now safe to use? I have been waiting to update until the crashing > issues were resolved because right now I have a pretty stable older versionâ¦ > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Feb. 13, 2018

Re: [Pharo-dev] Best VM for the Mac>

by Tudor Girba

Great news! Any idea of when this will make its way to the Pharo VM? Cheers, Doru > On Feb 13, 2018, at 4:18 PM, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > Hi Sean, > > On Feb 13, 2018, at 5:55 AM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> Stephane Ducasse-3 wrote >>> Well, do NOT rely on them on Sierra. >>> I can crash such VM while typing code. >>>>>>>> wget -O- get.pharo.org/vmLatest70 | bash >>>>>>>> wget -O- get.pharo.org/64/vmLatest70 | bash >> >> Are these now safe to use? I have been waiting to update until the crashing >> issues were resolved because right now I have a pretty stable older versionâ¦ > > > See https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/141 > >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> -- www.tudorgirba.com www.feenk.com âProgramming is executable philosophy."

Feb. 13, 2018

[Pharo 7.0-dev] Build #543: 21326-RubSmalltalkEditorfindClassFromAST-fallbackBlock-is-Undeclared-

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #543 was: SUCCESS. The Pull Request #877 was integrated: "21326-RubSmalltalkEditorfindClassFromAST-fallbackBlock-is-Undeclared-" Pull request url: https://github.com/pharo-project/pharo/pull/877 Issue Url: https://pharo.fogbugz.com/f/cases/21326 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 13, 2018