- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #559: Add tests for LargePositiveInteger&LargeNegativeInteger from last version of Squeak
by ci-pharo-ci-jenkins2＠inria.fr July 24, 2019

July 24, 2019

There is a new Pharo build available! The status of the build #559 was: SUCCESS. The Pull Request #4081 was integrated: "Add tests for LargePositiveInteger&LargeNegativeInteger from last version of Squeak" Pull request url: https://github.com/pharo-project/pharo/pull/4081 Issue Url: https://github.com/pharo-project/pharo/issues/clean Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #558: 2341-memory-leak-through-NECController-uniqueInstance
by ci-pharo-ci-jenkins2＠inria.fr July 24, 2019

July 24, 2019

There is a new Pharo build available! The status of the build #558 was: FAILURE. The Pull Request #4079 was integrated: "2341-memory-leak-through-NECController-uniqueInstance" Pull request url: https://github.com/pharo-project/pharo/pull/4079 Issue Url: https://github.com/pharo-project/pharo/issues/2341 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #557: Deprecate-PluggableTextMorph-and-subclasses
by ci-pharo-ci-jenkins2＠inria.fr July 24, 2019

July 24, 2019

There is a new Pharo build available! The status of the build #557 was: FAILURE. The Pull Request #4071 was integrated: "Deprecate-PluggableTextMorph-and-subclasses" Pull request url: https://github.com/pharo-project/pharo/pull/4071 Issue Url: https://github.com/pharo-project/pharo/issues/Deprecate Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

P8 + aTalent - aKind
by Norbert Hartl July 24, 2019

July 24, 2019

Iâm playing again with Talents and I want that in Pharo8 to appear so it can mature. I want to discuss a few things Iâm not clear about in order to help steering the talents in the right direction. I think Talents do not properly separate concerns. If you add a talent to an object each object gets its own anonymous class with its own method dictionary. To me this is two things at the same time. One use case I want is âruntime traitsâ. It means that you can add a trait at runtime to an object which acquires the functionality. But all objects of the same class + talent should share the same anonymous subclass. This would be possible in a performant way if I only want behavioral flexibility. It is just one more class per use case. A second step is âobject-centric behaviourâ which finally privatizes the method dictionary to one object making object-centric logging/debugging/â¦ possible. This is somewhat expensive but for object centric logging/debugging/â¦ there will be only a small amount of objects being extended. With Traits and now with Talents we need to rethink parts of the reflection API. We have #isKindOf: and #includesBehavior: which are not properly aligned at the moment [1] and for talents it gets even wrong. I think we need a definition what is a kind. What it means to include a behavior I find more straight forward. I used a few test classes Object subclass: #ContainsNoTrait instanceVariableNames: '' classVariableNames: '' package: 'Talents-Testâ Object subclass: #ContainsOneTrait uses: Doable instanceVariableNames: '' classVariableNames: '' package: 'Talents-Testâ Object subclass: #ContainsTwoTraits uses: Doable + Doable2 instanceVariableNames: '' classVariableNames: '' package: 'Talents-Testâ Trait named: #Doable uses: {} slots: { #status } package: 'Talents-Testâ Trait named: #Doable2 uses: {} slots: { #status2 } package: 'Talents-Testâ Code is attached. When I create instances of each noTrait := ContainsNoTrait new. oneTrait := ContainsOneTrait new. twoTraits := ContainsTwoTraits new. oneTalent := ContainsNoTrait new addTalent: Doable; yourself. twoTalents := ContainsNoTrait new addTalent: Doable + Doable2; yourself . and create a table of each behavior I get which doesnât look quite right. My opinion is that all of the #includesBehavior: calls should return true. Iâm not so sure about the #isKindOf: If we continue on that road the single class inheritance wonât be central to all of the code but a special quality. One of the composed elements can be a class with a superclass hierarchy. I donât know if there is a rationale that #includesBehavior: and #isKindOf: refer to that the same thing or not. It would be good to take the opportunity to make this a concept which gives back some symmetry again. Norbert [1] https://github.com/pharo-project/pharo/issues/3958 <https://github.com/pharo-project/pharo/issues/3958>

5 5

[Pharo 8.0] Build #556: Moved becomeForward from Object to ProtoObject where it belongs
by ci-pharo-ci-jenkins2＠inria.fr July 24, 2019

July 24, 2019

There is a new Pharo build available! The status of the build #556 was: SUCCESS. The Pull Request #4078 was integrated: "Moved becomeForward from Object to ProtoObject where it belongs" Pull request url: https://github.com/pharo-project/pharo/pull/4078 Issue Url: https://github.com/pharo-project/pharo/issues/4077 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #555: Speedup code loading for big packages
by ci-pharo-ci-jenkins2＠inria.fr July 24, 2019

July 24, 2019

There is a new Pharo build available! The status of the build #555 was: FAILURE. The Pull Request #4052 was integrated: "Speedup code loading for big packages" Pull request url: https://github.com/pharo-project/pharo/pull/4052 Issue Url: https://github.com/pharo-project/pharo/issues/speedup Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #554: Isolate references to Scheduler class variable in Delay
by ci-pharo-ci-jenkins2＠inria.fr July 24, 2019

July 24, 2019

There is a new Pharo build available! The status of the build #554 was: SUCCESS. The Pull Request #4047 was integrated: "Isolate references to Scheduler class variable in Delay" Pull request url: https://github.com/pharo-project/pharo/pull/4047 Issue Url: https://github.com/pharo-project/pharo/issues/Delay_Scheduler Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #553: 4060-RBParserparseErrorNode-uses-stop-position-not-start-to-create-ErrorNode
by ci-pharo-ci-jenkins2＠inria.fr July 24, 2019

July 24, 2019

There is a new Pharo build available! The status of the build #553 was: FAILURE. The Pull Request #4062 was integrated: "4060-RBParserparseErrorNode-uses-stop-position-not-start-to-create-ErrorNode" Pull request url: https://github.com/pharo-project/pharo/pull/4062 Issue Url: https://github.com/pharo-project/pharo/issues/4060 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #552: Migrate-ProfStef-to-Spec2
by ci-pharo-ci-jenkins2＠inria.fr July 24, 2019

July 24, 2019

There is a new Pharo build available! The status of the build #552 was: FAILURE. The Pull Request #4072 was integrated: "Migrate-ProfStef-to-Spec2" Pull request url: https://github.com/pharo-project/pharo/pull/4072 Issue Url: https://github.com/pharo-project/pharo/issues/Migrate Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #551: 4068-Cleanup-InfiniteForm
by ci-pharo-ci-jenkins2＠inria.fr July 23, 2019

July 23, 2019

There is a new Pharo build available! The status of the build #551 was: FAILURE. The Pull Request #4069 was integrated: "4068-Cleanup-InfiniteForm" Pull request url: https://github.com/pharo-project/pharo/pull/4069 Issue Url: https://github.com/pharo-project/pharo/issues/4068 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0