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

Re: [Pharo-dev] Proposal to remove [Stream|Collection]>>#write:

by Alistair Grant

On Fri, 22 Feb 2019 at 15:50, Esteban Maringolo <emaringolo(a)gmail.com> wrote: > > El vie., 22 feb. 2019 a las 11:43, ducasse > (<stepharo(a)netcourrier.com>) escribiÃ³: > > + 1 > > :) > > > But Iâm an easy person when it is about cleaning. > > +1. That makes us two. +1 Cheers, Alistair

Feb. 22, 2019

Re: [Pharo-dev] Proposal to remove [Stream|Collection]>>#write:

by Esteban Maringolo

El vie., 22 feb. 2019 a las 11:43, ducasse (<stepharo(a)netcourrier.com>) escribiÃ³: > + 1 > :) > But Iâm an easy person when it is about cleaning. +1. That makes us two.

Feb. 22, 2019

Re: [Pharo-dev] Proposal to remove [Stream|Collection]>>#write:

by ducasse

+ 1 :) But Iâm an easy person when it is about cleaning. > On 22 Feb 2019, at 15:39, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > Did you know that both Stream and Collection respond to #write: (as an alias to #<< and #add: respectively) ? I sure did not (and I did quite a bit of stream hacking). > > This selector is not used for these 2 receiver types in the standard image (except for one unit test), I never saw it being used in actual code. > > These are just aliases that add nothing but cognitive load. > > They make the API's of two important hierarchies (and especially the interface for non-inheriting classes) heavier than needed for no functional benefit. > > So I propose to remove [Stream|Collection]>>#write: > > What say thou ? > > Sven > >

Feb. 22, 2019

Proposal to remove [Stream|Collection]>>#write:

by Sven Van Caekenberghe

Hi, Did you know that both Stream and Collection respond to #write: (as an alias to #<< and #add: respectively) ? I sure did not (and I did quite a bit of stream hacking). This selector is not used for these 2 receiver types in the standard image (except for one unit test), I never saw it being used in actual code. These are just aliases that add nothing but cognitive load. They make the API's of two important hierarchies (and especially the interface for non-inheriting classes) heavier than needed for no functional benefit. So I propose to remove [Stream|Collection]>>#write: What say thou ? Sven

Feb. 22, 2019

[Pharo 8.0] Build #96: Small fix that slightly improves how the removal caption is createdâ¦

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

There is a new Pharo build available! The status of the build #96 was: SUCCESS. The Pull Request #2673 was integrated: "Small fix that slightly improves how the removal caption is createdâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/2673 Issue Url: https://pharo.fogbugz.com/f/cases/2567 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019

[Pharo 8.0] Build #95: 1967-critiques-icons-are-not-managed-correctly

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

There is a new Pharo build available! The status of the build #95 was: SUCCESS. The Pull Request #2655 was integrated: "1967-critiques-icons-are-not-managed-correctly" Pull request url: https://github.com/pharo-project/pharo/pull/2655 Issue Url: https://pharo.fogbugz.com/f/cases/1967 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019

[Pharo 8.0] Build #94: 2683-Remove-deprecated-pragma-to-use-deprecated-method

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

There is a new Pharo build available! The status of the build #94 was: SUCCESS. The Pull Request #2686 was integrated: "2683-Remove-deprecated-pragma-to-use-deprecated-method" Pull request url: https://github.com/pharo-project/pharo/pull/2686 Issue Url: https://pharo.fogbugz.com/f/cases/2683 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019

Remember to registrar to Pharo days 2019!

by Esteban Lorenzano

Dear all, Pharo days registration is open since two weeks now, and we are starting to work on the schedule and organising the social event :) Register now! Pharo days is a gathering of the Pharo community to exchange, discuss and code with your online colleagues. Join us to share your experiences and help to make a better Pharo! To register, please proceed to the Pharo Days 2019 web page: https://pharo.org/2019PharoDays <https://pharo.org/2019PharoDays>, or go directly to the association event: https://association.pharo.org/event-3255426 <https://association.pharo.org/event-3255426>. (Yes, the schedule is still to be defined, stay tuned). If there are any questions or problems, I am happy to answer them. Esteban

Feb. 22, 2019

[Pharo 8.0] Build #93: 2670-Update-the-checkVMVersion-date

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

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

Feb. 22, 2019

[Pharo 8.0] Build #92: 2668-Improve-some-randomly-failing-test-to-give-better-trace

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

There is a new Pharo build available! The status of the build #92 was: SUCCESS. The Pull Request #2669 was integrated: "2668-Improve-some-randomly-failing-test-to-give-better-trace" Pull request url: https://github.com/pharo-project/pharo/pull/2669 Issue Url: https://pharo.fogbugz.com/f/cases/2668 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019