- Pharo-dev - lists.pharo.org

This week (41/2020) on the Issue Tracker

by Marcus Denker

This week (41/2020) on the Issue Tracker ================================ Hi, We had the idea to try to do a summary of all the things that got merged during the week. I tried for a while an automatic tool (a Probot bot), but that only works for some weeks and then stops (I think they have some rate limiting problem for the bot). And it was not really usefulâ¦ as it just listed all PRs and Issues. This one puts a focus on *merged* PRs to Pharo itself only and sorts them by category with a little bit of context. Parser/Syntax Highlighting ======================= Improvement to make the prior huge improvement on parsing of syntactically wrong code much more usable: Several fixes to the parser and syntax feedback #7411 https://github.com/pharo-project/pharo/pull/7411 First class Variables / Compiler cleanup ==================== Lots of work has been done to unify all meta objects describing Variables into one hierarchy (see Variable and subclasses). This in turn enables many cleanups and simplification on the level of the name analysis of the Compiler and the API that the debugger uses to read Variables. Nearly finished, but some smaller steps remain: Variable-scope-addTests #7435 (all Variable objects should know the scope where they are from) https://github.com/pharo-project/pharo/pull/7435 Name Analysis: Lookup Slots In Class #7403 https://github.com/pharo-project/pharo/pull/7403 reduce-sends-doSemanticAnalysis #7402 https://github.com/pharo-project/pharo/pull/7402 7405-Debug-It-is-broken #7406 (this was a bad side effect of a refactoring needed to be able to move the call of #doSemanticAnalysis into the Compiler) https://github.com/pharo-project/pharo/pull/7406 Fluid Class Definions ====================== This is ongoing work to have a better class definiton for what is now called "slot enabeled class defintion" (the one where one can use First class Variables and where the Layout class is shown explicitly) 7444-Prepare-fluid-class-integration-part-4 #7445 https://github.com/pharo-project/pharo/pull/7445 7437-prepare-fluid-class-integration-part-3 #7438 https://github.com/pharo-project/pharo/pull/7438 7412-preparing-the-integration-of-fluid-class-part-2 #7434 https://github.com/pharo-project/pharo/pull/7434 7431-preparing-fluid-class-Part-1 #7433 https://github.com/pharo-project/pharo/pull/7433 Debugger ======= Debugger-should-show-Workspace-bindings #7408 A try to simplify how the workspace binding is found when debugging. Leads to many problems, will be reverted. https://github.com/pharo-project/pharo/pull/7408 7362-Package-Debugger-Filters-is-not-used-and-can-be-removed #7430 https://github.com/pharo-project/pharo/pull/7430 Added a closeAllDebugger method to trait TDebugger class, that users â¦ #7328 (just a first step, not yet solved) https://github.com/pharo-project/pharo/pull/7328 Exposing signalContext in Exception #7417 https://github.com/pharo-project/pharo/pull/7417 ReadOnly Literals ================= The compiler and the VM has support to make literals read-only. As the ability to change literals without the code reflecting it has lead to ugly bugs in the past, turning this on looks like a good idea: SourceFileBufferedReadWriteStreamTest-readOnlyLiteral #7418 https://github.com/pharo-project/pharo/pull/7418 betterName-isSharedLiteral #7432 https://github.com/pharo-project/pharo/pull/7432 Enable-ReadOnly-Literals #7393 https://github.com/pharo-project/pharo/pull/7393 Bug Fixes ========== Background failures log in CI #7337 https://github.com/pharo-project/pharo/pull/7337 5956-Wrong-format-of-DoubleWordArray #7404 Ongoing work. All code is merged, but now we need to still see that we can create classes like that with the bootrap https://github.com/pharo-project/pharo/pull/7404 Fix_for_PluggableSliderMorph #7415 https://github.com/pharo-project/pharo/pull/7415 7414-division-of-number-by-array-fails-with-doesNotUnderstand-isZero #7425 https://github.com/pharo-project/pharo/pull/7425 Cleaning integer division #7436 https://github.com/pharo-project/pharo/pull/7436 Comments ======== 7042-Better-comment-for-CompiledBlock-and-FullBlock https://github.com/pharo-project/pharo/pull/7447 Cleanups ======== 7367-pragmas-not-needed-textEditorShiftedMenu-fileListContentMenu #7426 https://github.com/pharo-project/pharo/pull/7426 Fixed #7420. Added transformation rules to some non-transforming deprecations that were identified as automatable in the Deprewriter paper #7427 https://github.com/pharo-project/pharo/pull/7427 7364-RBSelectorNode-has-unclassified-methods #7424 https://github.com/pharo-project/pharo/pull/7424 7416-Fileout-a-protocol-raises-a-DNU #7441 https://github.com/pharo-project/pharo/pull/7441 7365-DictionaryValueHold-removeKey-calls-a-non-existing-method #7407 https://github.com/pharo-project/pharo/pull/7407 For a complete list of all issues and PRs, see: https://github.com/pharo-project/pharo/pulse

Oct. 9, 2020

Re: Super nice parser improvements soon available

by Tim Mackinnon

That is awesome work - I love you guys for continuing to improve this stuff! Itâs inspiring... Tim > On 3 Oct 2020, at 10:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > ï»¿ > >> In the last week Iâve worked on doing several enhances to the parser >> >> https://github.com/pharo-project/pharo/pull/7411 >> >> Besides several refactorings and cleanups, major changes include: >> >> - we are able to correctly detect unfinished statements (missing dots) >> - we are able to correctly detect unreachable statements (like a statement after a return statement) >> >> And we still continue parsing. This makes that the faulty parser used for syntax highlighting and other much more precise, and several of my touches also fix some of the exceptions found while typing (that were due to wrong behaviours on the parser). >> >> Also I did a small iteration on top of the âsyntax feedbackâ so itâs less noisy. We can remove it at any time (thatâs just removing a configuration). But Iâd like more feedback before :) >> >> To see the improvements >> >> Pharo 8 >> >> <PastedGraphic-3.png> >> >> Pharo9 previous to these changes >> >> <PastedGraphic-1.png> >> >> Pharo9 with these changes >> >> <PastedGraphic-2.png> >> >> >> Now, Iâll not deny this is still perfectible, as everything, but we can do another iteration on top :) >> >> Guille >> _______________________________________________ >> Lse-consortium mailing list >> Lse-consortium(a)lists.gforge.inria.fr >> https://lists.gforge.inria.fr/mailman/listinfo/lse-consortium > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France >

Oct. 3, 2020

Super nice parser improvements soon available

by StÃ©phane Ducasse

> In the last week Iâve worked on doing several enhances to the parser > > https://github.com/pharo-project/pharo/pull/7411 <https://github.com/pharo-project/pharo/pull/7411> > > Besides several refactorings and cleanups, major changes include: > > - we are able to correctly detect unfinished statements (missing dots) > - we are able to correctly detect unreachable statements (like a statement after a return statement) > > And we still continue parsing. This makes that the faulty parser used for syntax highlighting and other much more precise, and several of my touches also fix some of the exceptions found while typing (that were due to wrong behaviours on the parser). > > Also I did a small iteration on top of the âsyntax feedbackâ so itâs less noisy. We can remove it at any time (thatâs just removing a configuration). But Iâd like more feedback before :) > > To see the improvements > > Pharo 8 > > > > Pharo9 previous to these changes > > > > Pharo9 with these changes > > > > > Now, Iâll not deny this is still perfectible, as everything, but we can do another iteration on top :) > > Guille > _______________________________________________ > Lse-consortium mailing list > Lse-consortium(a)lists.gforge.inria.fr > https://lists.gforge.inria.fr/mailman/listinfo/lse-consortium -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Oct. 3, 2020

Re: beta testers for the new version of the Pharo mooc

by tbrunz

Hi Stef, Do you have information on the schedule yet? (Times of day) I'm asking people, and they want to know how much time/how to schedule this. Thanks, -Ted -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Oct. 3, 2020

Re: beta testers for the new version of the Pharo mooc

by Christopher Fuhrman

Hi Stef, At the very least I can help, but I will try to find some students. I just upgraded to WSL2 on Windows 10 and would like to see how Pharo performs. C. Fuhrman On Wed, Sep 30, 2020, 10:30 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hello guys > > We are looking for beta tester for the new version of the Pharo mooc. > The beta test period is planned from 12 to 23 of october > Let me know if you can help. > > Tx > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > >

Oct. 1, 2020

Re: beta testers for the new version of the Pharo mooc

by Juan Pablo Sandoval Alcocer

Hi Stef, Daniel (in copy), one of my students, is willing to help. He started with Pharo one year ago, he also read the previous version of Pharo mooc. Regards, Juan P. El miÃ©., 30 sept. 2020 a las 10:30, StÃ©phane Ducasse (< stephane.ducasse(a)inria.fr>) escribiÃ³: > Hello guys > > We are looking for beta tester for the new version of the Pharo mooc. > The beta test period is planned from 12 to 23 of october > Let me know if you can help. > > Tx > > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr / http://www.pharo.org > 03 59 35 87 52 > Assistant: Aurore Dalle > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > >

Oct. 1, 2020

Re: [ANN] Pharo Consortium New Gold Member: InfOil

by Esteban Maringolo

As a former employee of the company I'm really happy to see this finally happening! Best regards! Esteban A. Maringolo On Wed, Sep 30, 2020 at 11:13 AM Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > The Pharo Consortium is very happy to announce that InfOil has joined the Consortium as a Gold Member. > > InfOil is an Argentinian company focused on software development for the Oil and Gas industry with clients > in Latin America, Cuba, and Canada. > > About > - InfOil: http://www.infoil.com.ar > - 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

Sept. 30, 2020

beta testers for the new version of the Pharo mooc

by StÃ©phane Ducasse

Hello guys We are looking for beta tester for the new version of the Pharo mooc. The beta test period is planned from 12 to 23 of october Let me know if you can help. Tx -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

Sept. 30, 2020

[ANN] Pharo Consortium New Gold Member: InfOil

by Marcus Denker

The Pharo Consortium is very happy to announce that InfOil has joined the Consortium as a Gold Member. InfOil is an Argentinian company focused on software development for the Oil and Gas industry with clients in Latin America, Cuba, and Canada. About - InfOil: http://www.infoil.com.ar - 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

Sept. 30, 2020

[ANN] Next Pharo Sprint: Sept 25

by Marcus Denker

We will organize a Pharo sprint / Moose dojo Sept 25 (this Friday) Goals of this sprint: - Fix issues from tracker https://github.com/pharo-project/pharo/issues This is a Remote Sprint, it happens on Discord. http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 A list of all Pharo Event of the year an be found here: https://association.pharo.org/events

Sept. 22, 2020