- Pharo-dev - lists.pharo.org

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

by Sven Van Caekenberghe

> On 22 Feb 2019, at 19:39, Stephan Eggermont <stephan(a)stack.nl> wrote: > > Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > . >> >> So I propose to remove [Stream|Collection]>>#write: >> >> What say thou ? > > Check the selectors used in the latest packages on squeaksource, ss3, > smalltalkhub and decide. > > Stephan You forgot GitHub and all private company repositories in the world.

Feb. 22, 2019

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

by Stephan Eggermont

Sven Van Caekenberghe <sven(a)stfx.eu> wrote: . > > So I propose to remove [Stream|Collection]>>#write: > > What say thou ? Check the selectors used in the latest packages on squeaksource, ss3, smalltalkhub and decide. Stephan

Feb. 22, 2019

[Pharo 8.0] Build #99: 2645-Duplication-wrappingPolicyLabel-and-lineNumbersDisplayLabel-is-defined-4-times

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

There is a new Pharo build available! The status of the build #99 was: FAILURE. The Pull Request #2662 was integrated: "2645-Duplication-wrappingPolicyLabel-and-lineNumbersDisplayLabel-is-defined-4-times" Pull request url: https://github.com/pharo-project/pharo/pull/2662 Issue Url: https://pharo.fogbugz.com/f/cases/2645 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019

[Pharo 8.0] Build #98: 2680-Cleanup-and-streamline-semantics-of-WriteStream-and-putOn-

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

There is a new Pharo build available! The status of the build #98 was: FAILURE. The Pull Request #2698 was integrated: "2680-Cleanup-and-streamline-semantics-of-WriteStream-and-putOn-" Pull request url: https://github.com/pharo-project/pharo/pull/2698 Issue Url: https://pharo.fogbugz.com/f/cases/2680 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019

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

by Sven Van Caekenberghe

https://github.com/pharo-project/pharo/issues/2701 > On 22 Feb 2019, at 15:57, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > 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

[Pharo 8.0] Build #97: 2677-Add-a-setting-to-disable-the-world-menu

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

There is a new Pharo build available! The status of the build #97 was: SUCCESS. The Pull Request #2678 was integrated: "2677-Add-a-setting-to-disable-the-world-menu" Pull request url: https://github.com/pharo-project/pharo/pull/2678 Issue Url: https://pharo.fogbugz.com/f/cases/2677 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Feb. 22, 2019

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