- Pharo-dev - lists.pharo.org

Added a GitHub project board for Debugger related issue

by Marcus Denker

Hi, I added a Project Board for âDebugger and Debuggingâ: https://github.com/orgs/pharo-project/projects/23 <https://github.com/orgs/pharo-project/projects/23> To edit the board, one has to be a member of the organizion, if you are not but would like to edit: I can add you. Marcus

July 1, 2019

[ANN] Pharo Consortium New Academic Member: Universidad CatÃ³lica Boliviana - Cochabamba

by Marcus Denker

The Pharo Consortium is very happy to announce that IngenierÃa de Sistemas, Universidad CatÃ³lica Boliviana - Cochabamba has joined the Consortium as an Academic Member. About - IngenierÃa de Sistemas, Universidad CatÃ³lica Boliviana - Cochabamba https://www.ucbcba.edu.bo/ - 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

July 1, 2019

[Pharo 8.0] Build #417: FAILURE

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

There is a new Pharo build available! The status of the build #417 was: FAILURE. Could not extract further issue information from commit message: Fixing the traits implementation. When there is a diamond definition of a slot, it should not be a conflict. Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 1, 2019

Re: [Pharo-dev] A small game: do one trivial improvement every day

by Marcus Denker

> On 1 Jul 2019, at 09:59, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 1 Jul 2019, at 08:45, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> For the ones I add for other to do I put the âEasyâ tag and add them to this GitHub project (kanban board): >> >> https://github.com/orgs/pharo-project/projects/8 >> > And two issue for someone to do: - allBehaviorsDo: can now use the cached allBehaviors https://github.com/pharo-project/pharo/issues/3726 simple, but quite some impact (we should of course refactor all the senders of allBehaviorsDo: later as they now can be transformed to use collection methods and be even faster then do:â¦) and a slightly harder one: add #whichMethodsReferTo: https://github.com/pharo-project/pharo/issues/3727 nearly all clients of thoroughWhichSelectorsReferTo: are interested in the methods, not the selector. we should add #whichMethodsReferTo: and rewrite the clients to use that instead. Marcus

July 1, 2019

Re: [Pharo-dev] A small game: do one trivial improvement every day

by Marcus Denker

> On 1 Jul 2019, at 08:45, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > For the ones I add for other to do I put the âEasyâ tag and add them to this GitHub project (kanban board): > > https://github.com/orgs/pharo-project/projects/8 > Small fix Friday: ============= 3700-simplify-allUnreferencedInstanceVariables https://github.com/pharo-project/pharo/pull/3701/files same idea as the class vars, now that variables are object, bit strings, we can implement it simply as: ^self allSlots reject: [:slot | slot isReferenced] (and it will returns object, that e.g. know the class they are declared in) Saturday ======= I did one of the simple ones posted the day before: 3630-small-cleanup-traits-in-Behaviour-isComposedBy-move-to-traits https://github.com/pharo-project/pharo/pull/3704 Then I did a small (one var added, two lines changed)l, but definitely not trivial improvement: SystemDictionary: add a cache for allBehaviors https://github.com/pharo-project/pharo/issues/3702 Right now SystemDictionary caches names, we should cache Objects instead. this is the first step. And it enables Sunday =================== speedup "implementors of https://github.com/pharo-project/pharo/pull/3711 With the allBehaviors cache, we can radically simplify (and speedup!) a lot of code used very very often. [#name implementors] bench before: "'69.688 per second'" after: "'119.385 per second'" The new implementation is this: SystemNavigation>>allImplementorsOf: aSelector "Answer all the methods that implement the message aSelector." ^self allBehaviors select: [:class | class includesSelector: aSelector] thenCollect: [:class | (class>>aSelector) methodReference ] This #allBehaviors cache will allow many more simplifications (check senders of #allBehaviorsDo:) e.g. for today, I did two as part of this (isUnsentMessage: and allPrimitiveMethods): https://github.com/pharo-project/pharo/pull/3725/files Marcus

July 1, 2019

Re: [Pharo-dev] A small game: do one trivial improvement every day

by Marcus Denker

For the ones I add for other to do I put the âEasyâ tag and add them to this GitHub project (kanban board): https://github.com/orgs/pharo-project/projects/8 <https://github.com/orgs/pharo-project/projects/8> > On 29 Jun 2019, at 18:11, Serge Stinckwich <serge.stinckwich(a)gmail.com> wrote: > > Can we define a tag for such issues ? > > > On Fri, Jun 28, 2019 at 9:37 PM Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > > > > > Trivial improvement of the day: > > > > simplify #allSelectorsInProtocol: > > https://github.com/pharo-project/pharo/pull/3647 <https://github.com/pharo-project/pharo/pull/3647> > > > > has been merged. > > > > > > Trivial thing to do for someone else: > > > > #zapAllMethods can be removed > > https://github.com/pharo-project/pharo/issues/3656 <https://github.com/pharo-project/pharo/issues/3656> > > > > was done (not by me!) and merged! > > Trivial thing done today: > > simplify allUnreferencedClassVariables > https://github.com/pharo-project/pharo/issues/3661 <https://github.com/pharo-project/pharo/issues/3661> > > this is a nice example how other trivial unimportant changes make things trivial that where not trivial before. > After > - adding #isReferenced for class variables (https://github.com/pharo-project/pharo/pull/3653 <https://github.com/pharo-project/pharo/pull/3653>) > - adding #allClassVariables for classes (https://github.com/pharo-project/pharo/pull/3658 <https://github.com/pharo-project/pharo/pull/3658>) > > this was trivial. So I guess doing trivial things (that you might think are not important because they are oh so trivial) actually > have the effect to make something trivial that was not trivial before? That is oddâ¦ > > Trivial thing for someone else to do: > > fix typo in Welcome bot message: ârunnâ > https://github.com/pharo-project/pharo/issues/3696 <https://github.com/pharo-project/pharo/issues/3696> > > One of the welcome bot messages has a typo: ârunn" should be ârun" > > This needs to be fixed here: > > https://github.com/pharo-project/pharo/blob/Pharo8.0/.github/config.yml <https://github.com/pharo-project/pharo/blob/Pharo8.0/.github/config.yml> > > the file can be edited right from the GitHub interface > > > Marcus > > > > > -- > Serge Stinckwicâhâ > Int. Research Unit on Modelling/Simulation of Complex Systems (UMMISCO) > âSorbonne University (SU) > French National Research Institute for Sustainable Development (IRD)â > Uâniversity of YaoundÃ© Iâ, Cameroon > "Programs must be written for people to read, and only incidentally for machines to execute." > https://twitter.com/SergeStinckwich <https://twitter.com/SergeStinckwich> > â

July 1, 2019

[Pharo 8.0] Build #416: Cleanup System-BasicCommandLineHandler-Tests

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

There is a new Pharo build available! The status of the build #416 was: FAILURE. The Pull Request #3717 was integrated: "Cleanup System-BasicCommandLineHandler-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/3717 Issue Url: https://github.com/pharo-project/pharo/issues/3716 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 1, 2019

[Pharo 8.0] Build #415: 3708-cleanup-SystemNavigationTest

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

There is a new Pharo build available! The status of the build #415 was: SUCCESS. The Pull Request #3709 was integrated: "3708-cleanup-SystemNavigationTest" Pull request url: https://github.com/pharo-project/pharo/pull/3709 Issue Url: https://github.com/pharo-project/pharo/issues/3708 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 1, 2019

Re: [Pharo-dev] [Pharo 8.0] Build #412: Making the World to render in different backends

by Ronie Salgado

This PR looks really cool. El sÃ¡b., 29 jun. 2019 a las 22:43, Sean P. DeNigris (<sean(a)clipperadams.com>) escribiÃ³: > ci-pharo-ci-jenkins2 wrote > > The Pull Request #3627 was integrated: "Making the World to render in > > different backends" > > Sounds cool :) > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

June 30, 2019

[Pharo 8.0] Build #414: 3706-INVALID-ISSUE

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

There is a new Pharo build available! The status of the build #414 was: SUCCESS. The Pull Request #3707 was integrated: "3706-INVALID-ISSUE" Pull request url: https://github.com/pharo-project/pharo/pull/3707 Issue Url: https://github.com/pharo-project/pharo/issues/3706 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 30, 2019