- Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #308: 20721 Unused temps in ProtoObject>>#pointersToExcept:
by ci-pharo-ci-jenkins2＠inria.fr Nov. 18, 2017

Nov. 18, 2017

There is a new Pharo build available! The status of the build #308 was: SUCCESS. The Pull Request #501 was integrated: "20721 Unused temps in ProtoObject>>#pointersToExcept:" Pull request url: https://github.com/pharo-project/pharo/pull/501 Issue Url: https://pharo.fogbugz.com/f/cases/20721 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #307: 20715 Unused temps in RBRefactoringChangeTests, RPackageClassesSynchronisationTest, RPackageIncrementalTest, ...
by ci-pharo-ci-jenkins2＠inria.fr Nov. 18, 2017

Nov. 18, 2017

There is a new Pharo build available! The status of the build #307 was: SUCCESS. The Pull Request #495 was integrated: "20715 Unused temps in RBRefactoringChangeTests, RPackageClassesSynchronisationTest, RPackageIncrementalTest, ..." Pull request url: https://github.com/pharo-project/pharo/pull/495 Issue Url: https://pharo.fogbugz.com/f/cases/20715 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #306: 20714-atatput--atatifAbsentPut-should-not-use-Dictionary
by ci-pharo-ci-jenkins2＠inria.fr Nov. 18, 2017

Nov. 18, 2017

There is a new Pharo build available! The status of the build #306 was: SUCCESS. The Pull Request #496 was integrated: "20714-atatput--atatifAbsentPut-should-not-use-Dictionary" Pull request url: https://github.com/pharo-project/pharo/pull/496 Issue Url: https://pharo.fogbugz.com/f/cases/20714 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo and special unary selectors
by Torsten Bergmann Nov. 17, 2017

Nov. 17, 2017

Hi, just something to think about: one thing I always liked about Smalltalk is that it allows for nice DSL's. We have nice things like a unit framework in Pharo, ... In the most simple case one can easily implement own units just by providing a unary messages: 1 m 1 second 1 px 1 EUR One can easily implement an own Money class with a currency and then do polymorphic tricks like 10 EUR + 20 EUR But we can currently can not implement special unary selectors (including special unary selectors with unicode) like: 100 % 20 $ 40 â¬ 12 â° (for promille) Especially things like 20 % would be nice for layout issues or other (Bloc comes to mind). Maybe we should put that on the roadmap of Pharo because IMHO it would be cool to support such things in the future. Dont know how much effort it currently means on the technical level but maybe others can comment. Thx T.

8 12

Little Chapter on Hash methods
by Stephane Ducasse Nov. 17, 2017

Nov. 17, 2017

Hi As part of a large effort to offer more documentation to Pharo and clean all the nearly finish works I started but never finishr. In the tips and tricks booklet, I added a simple chapter on hash. Comment and PullRequests are welcome. Stef

2 2

[Pharo 7.0-dev] Build #305: 20709-do-not-create-pharo-core-symlink-during-the-image-building
by ci-pharo-ci-jenkins2＠inria.fr Nov. 17, 2017

Nov. 17, 2017

There is a new Pharo build available! The status of the build #305 was: SUCCESS. The Pull Request #492 was integrated: "20709-do-not-create-pharo-core-symlink-during-the-image-building" Pull request url: https://github.com/pharo-project/pharo/pull/492 Issue Url: https://pharo.fogbugz.com/f/cases/20709 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #304: 20704-remove-garbageCollect-from-PharoClassInstallermigrateClassestousing
by ci-pharo-ci-jenkins2＠inria.fr Nov. 17, 2017

Nov. 17, 2017

There is a new Pharo build available! The status of the build #304 was: SUCCESS. The Pull Request #489 was integrated: "20704-remove-garbageCollect-from-PharoClassInstallermigrateClassestousing" Pull request url: https://github.com/pharo-project/pharo/pull/489 Issue Url: https://pharo.fogbugz.com/f/cases/20704 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Dark Mode List
by Sven Van Caekenberghe Nov. 17, 2017

Nov. 17, 2017

Although, de gustibus non est disputandum, I am happy we fit right in: https://www.darkmodelist.com <https://www.darkmodelist.com/> -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org <http://pharo.org/> http://association.pharo.org http://consortium.pharo.org

3 4

Re: [Pharo-dev] [Pharo-users] why is adding instance variables so slow?
by Tudor Girba Nov. 17, 2017

Nov. 17, 2017

Hi, Please letâs move this discussion on pharo-dev. And keep going :) Cheers, Doru > On Apr 14, 2017, at 12:09 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > > 2017-04-14 11:09 GMT+02:00 tesonep(a)gmail.com <tesonep(a)gmail.com>: > Hi, I think the problem was not clearly explained. This is the scenario that is problematic. > This scenario does not happen in the new Spur implementation of forwarding, but I think is happening in the old one. > > 1. You have, let's say 3 instances of ClassA. > 2. You add a new instance variable to ClassA. It produces > 2a. A new ClassAv2 is created with the instances variables of ClassA and the newone > 2b. 3 Instances of ClassAv2 are created > 2c. The values of the instance variables of ClassA are copied to the ones in ClassAv2 (the ones missing are left in nil). > 2d. The 3 instances of ClassA are becomed forward to the 3 instances of ClassAv2 > 2e. The ClassA is becomed forward ClassAv2 > > I still not see why my example not reflects all these steps. I checked also scenario with class becoming: > > c1 := Class1 new. > c2 := Class2 new. > c1 becomeForward: c2. > Class1 becomeForward: Class2. > Class2 allInstances "=>#(aClass2)" > > It also works in Cog -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."

3 2

Pharo Quality: raising the quality level in Pharo 7 and onwards
by Torsten Bergmann Nov. 17, 2017

Nov. 17, 2017

Hi, when we forked Pharo back in the days (2008) one of the primary goals of Pharo was and still is to provide a CLEAN SYSTEM. Now after nearly 10 years we have done already an amazing job. But we are still not there. While it is a good thing that we rewrite parts of the image, work on bootstrap and new shiny tools I unfortunately see the effect that even some newly written code has flaws or is not meeting some basic quality standards like: - having class comments - no uncategorized methods anymore - not having unused temps or unused instance variables - tests in a separate package than the code (to be able to have minified versions without tests) - class instance variable naming in lowercase - ... Meanwhile in Pharo 6 and 7 there are nice tools inside to check your code. So USE THEM. Some of you have already seen that I continue to do more and more of such cleanups in the system in various Pharo 7 contributions. Believe me: this is a boring task and one can earn much more applause for other nice and more amazing contributions - but the dirty job needs to be done to clean up the house. I also started to integrate some more "Release Tests" to make sure the things cleaned now stay clean over time and is not violated again by new Pull requests or new package inclusions. Because some of these cleanups were already done in Pharo 5 and 6 - but violated again by new contributions we now need to enforce that the image stays at that qualit level. Because I do not want to waste my time to do it over and over again! See package "ReleaseTests" or code like ProperMethodCategorizationTest, ProperlyImplementedClassesTest, #testAllClassInstanceVariablesStartLowercase and other which was written to ensure we not only GET better but also STAY better in the future. Thanks to Pavel, Marcus, Esteban and others for reviewing and integrating. Still there is a long journey in front of us, some examples: 1. Unused Temps CompiledMethod allInstances select: [:m | m ast temporaries anySatisfy: [:x | x binding isUnused ]]. => over 200 still 2. Uncategorized methods Object allSubclasses select: [:each | (each selectorsInProtocol: Protocol unclassified) notEmpty ] => over 200 still 3. Many many more uncommented classes. We need a special reminder to people who can write many code lines a day but are not able to spend a minute to write a class comment. 4. ... One person will require too much time ... several contributors helping with one contribution a day or a week will already change the game and make it possible again. Why not have a clean base image meeting basic criterias by the end of the year 2017 and ensuring with tests that we continue clean in 2018? Would'nt this be a nice birthday present to Pharos 10 years anniversary in 2018? How can you help: ================= a) you can check you own packages using the provided quality tools and before you integrate new features just cleanup your code first b) even as beginners you can help cleaning up such easy things and with simple cleanup pull requests help moving Pharo 7 forward c) you can think of other short snippets that reveal design or code flaws and post them here Then we can fix these in the image too and have the rules enforced using a separate release test d) lets discuss and define quality criterias and note them somewhere e) ideally you can reveal problems, open bugs, clean them up and then write Release tests to ensure we stay clean We should and need to definitely raise the bar. I would even be more radical to enforce more quality: - in the worst case we should not accept contributions or put new versions of packages into the image when they do not meet basic criterias, that is the idea of the release tests - if parts of the community are not seeing this as a necessity then in the worst case we need to fork Pharo again into another next level CLEANED UP system ;) So PLEASE HELP!!! Otherwise this will KILL US and it also will be and ENDLESS journey for a few people to try to clean the house. So PLEASE HELP before you work on the next shiny feature that might still violates the basics making this an impossible journey for others to move forward on that frontier. Bye T.

5 5