- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Proposal to remove [Stream|Collection]>>#write:
by Sven Van Caekenberghe Feb. 25, 2019

Feb. 25, 2019

<intellectual response> Many system classes contain lots of methods that are confusing, duplicates of similar functionality, bogus, old, unused, untested and undocumented . This makes the system more complex, especially for newcomers, but also for everyone else trying to make changes. This is often technical debt, cleanup that has been postponed. It is important that knowledgeable developers try to clean up by simplifying things. If not, the situation will never improve. Of course we have to be careful, in this particular case I was. We have done many hundreds of these removals in the past years, with very little problems. We have also done way more dangerous things, like change signatures and semantics of existing methods. In my opinion we can safely go ahead and remove this. A couple of others concurred. If someone wants to go through the trouble to do this with deprecation and a rewrite rule, fine. <emotional response> Sure, the responses "Trying to be *somewhat* compatible and verifying (even quickly) that it's not breaking a gazillion things is the very least someone can do... Backward compatibility is NOT a sin! ;):" and "Check the selectors used in the latest packages on squeaksource, ss3, smalltalkhub and decide." are pure technical, intellectual arguments and not passive-aggressive criticism. Right. > On 22 Feb 2019, at 19:54, Benoit St-Jean via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > Subject: Re: [Pharo-dev] Proposal to remove [Stream|Collection]>>#write: > Date: 22 February 2019 at 19:54:55 GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > > Trying to be *somewhat* compatible and verifying (even quickly) that it's not breaking a gazillion things is the very least someone can do... Backward compatibility is NOT a sin! ;) > > On 2019-02-22 13:45, Sven Van Caekenberghe wrote: >> >>> 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. >> >> > -- > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > >

3 2

bootstrap desync information?
by ducasse Feb. 24, 2019

Feb. 24, 2019

Hi guys Ideally I would like to add a simple and little package with DisplayableObject because I do not want to put it in the System-Model package. I was wondering what is the impact on the bootstrap and I think that the impact is null since BaselineOfBootstrap does not contain System-Model but only UIManager. Now I found in the rule checker that System-Model is listed there and I found that it could be a desync between the information. What do you think? Now I have the impression that for now I could try to keep DisplayableObject with Model in System-Model and see how it goes. Because the decomposition between the different baseline is still something that need some iterations. Stef bootstrapPackages ^ #( #'AST-Core' #'Announcements-Core' #CodeExport #CodeImport #CodeImportCommandLineHandlers #Collections #Compression #'FileSystem-Core' #'FileSystem-Disk' #Files #Jobs #Kernel #Monticello #'Multilingual-Encodings' #'Multilingual-Languages' #'Multilingual-TextConversion' #'Network-UUID' #'OpalCompiler-Core' #'Random-Core' #'RPackage-Core' #'Ring-Deprecated-Core-Containers' #'Ring-Deprecated-Core-Kernel' #'Ring-Deprecated-Monticello' #'Ring-Deprecated-ChunkImporter' #'Slot-Core' #'System-Announcements' #'System-BasicCommandLineHandler' #'System-Changes' #'System-CommandLine' #'System-CommandLineHandler' #'System-Finalization' #'System-Hashing' #'System-Localization' #'System-Model' #'System-Platforms' #'System-SessionManager' #'System-Sources' #'System-Support' #Traits #'Transcript-Core' #UIManager #'Collections-Abstract' #'Collections-Arithmetic' #'Collections-Native' #'Collections-Sequenceable' #'Collections-Stack' #'Collections-Streams' #'Collections-Strings' #'Collections-Support' #'Collections-Unordered' #'Collections-Weak' #'Zinc-Character-Encoding-Core' #'Zinc-Resource-Meta-Core' #'PharoBootstrap-Initialization' #'Transcript-NonInteractive' ) Stef

1 1

[Pharo 8.0] Build #105: 2712-Retrying
by ci-pharo-ci-jenkins2＠inria.fr Feb. 24, 2019

Feb. 24, 2019

There is a new Pharo build available! The status of the build #105 was: FAILURE. The Pull Request #2714 was integrated: "2712-Retrying" Pull request url: https://github.com/pharo-project/pharo/pull/2714 Issue Url: https://pharo.fogbugz.com/f/cases/2712 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #104: 2659-Update-and-rename-KmGlobalDispatcherclassst-to-KMGlobalDispatcherc
by ci-pharo-ci-jenkins2＠inria.fr Feb. 23, 2019

Feb. 23, 2019

There is a new Pharo build available! The status of the build #104 was: SUCCESS. The Pull Request #2710 was integrated: "2659-Update-and-rename-KmGlobalDispatcherclassst-to-KMGlobalDispatcherc" Pull request url: https://github.com/pharo-project/pharo/pull/2710 Issue Url: https://pharo.fogbugz.com/f/cases/2659 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #103: 2578-Test-result-notification-uses-wrong-plural-forms
by ci-pharo-ci-jenkins2＠inria.fr Feb. 23, 2019

Feb. 23, 2019

There is a new Pharo build available! The status of the build #103 was: FAILURE. The Pull Request #2695 was integrated: "2578-Test-result-notification-uses-wrong-plural-forms" Pull request url: https://github.com/pharo-project/pharo/pull/2695 Issue Url: https://pharo.fogbugz.com/f/cases/2578 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #102: More reasonable timespan arithmetic
by ci-pharo-ci-jenkins2＠inria.fr Feb. 23, 2019

Feb. 23, 2019

There is a new Pharo build available! The status of the build #102 was: SUCCESS. The Pull Request #2497 was integrated: "More reasonable timespan arithmetic" Pull request url: https://github.com/pharo-project/pharo/pull/2497 Issue Url: https://pharo.fogbugz.com/f/cases/2458 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #101: 2704-Improve-as-when-the-class-is-already-of-the-right-kind
by ci-pharo-ci-jenkins2＠inria.fr Feb. 23, 2019

Feb. 23, 2019

There is a new Pharo build available! The status of the build #101 was: FAILURE. The Pull Request #2705 was integrated: "2704-Improve-as-when-the-class-is-already-of-the-right-kind" Pull request url: https://github.com/pharo-project/pharo/pull/2705 Issue Url: https://pharo.fogbugz.com/f/cases/2704 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #100: 2688-Remove-GLMExamplesBrowser-and-GLMExamples
by ci-pharo-ci-jenkins2＠inria.fr Feb. 22, 2019

Feb. 22, 2019

There is a new Pharo build available! The status of the build #100 was: SUCCESS. The Pull Request #2702 was integrated: "2688-Remove-GLMExamplesBrowser-and-GLMExamples" Pull request url: https://github.com/pharo-project/pharo/pull/2702 Issue Url: https://pharo.fogbugz.com/f/cases/2688 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Proposal to remove [Stream|Collection]>>#write:
by Sven Van Caekenberghe Feb. 22, 2019

Feb. 22, 2019

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

7 8

[Pharo 8.0] Build #99: 2645-Duplication-wrappingPolicyLabel-and-lineNumbersDisplayLabel-is-defined-4-times
by ci-pharo-ci-jenkins2＠inria.fr Feb. 22, 2019

Feb. 22, 2019

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…

1 0