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

[Pharo 8.0] Build #661: psKeysSemaSimplify
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

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

1 0

[Pharo 8.0] Build #660: Push-down-method-on-right-owner
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

There is a new Pharo build available! The status of the build #660 was: FAILURE. The Pull Request #4379 was integrated: "Push-down-method-on-right-owner" Pull request url: https://github.com/pharo-project/pharo/pull/4379 Issue Url: https://github.com/pharo-project/pharo/issues/Push Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #659: Use stack instead of recursion in MCScanner>>next
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

There is a new Pharo build available! The status of the build #659 was: SUCCESS. The Pull Request #4310 was integrated: "Use stack instead of recursion in MCScanner>>next" Pull request url: https://github.com/pharo-project/pharo/pull/4310 Issue Url: https://github.com/pharo-project/pharo/issues/MCScanner_next Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Pharo Consortium New Bronze Member: Object Guild
by Marcus Denker Aug. 22, 2019

Aug. 22, 2019

The Pharo Consortium is very happy to announce that the Object Guild has joined the Consortium as a Bronze Member. Object Guild Simply Revolutionary High fidelity software solutions for values-driven organisations. We help you to help the world become a better place. Object Guild differentiates itself as a custom software design and development shop in the following ways: - by a commitment to use technology and software to make the world a better place; - by seeking and serving clients who are equally committed to social and environmental enhancement; - by focusing on "Software that Fits," that seamlessly integrates with and enhances the complex system where it is deployed; - by our commitment to Pharo and Smalltalk development, including expanding and enhancing Pharo; - by a focus on education and training, internal and for clients, that advances the "state-of-the-practice" of software development. https://objectguild.com The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. http://consortium.pharo.org Individuals can support Pharo via the Pharo Association. http://association.pharo.org

1 0

[Pharo 7.0] Build #169: 4282-Backport-Pharo7-trying-to-add-an-ivar-to-UndefinedObject-crashes-the-VM-4017
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

There is a new Pharo build available! The status of the build #169 was: FAILURE. The Pull Request #4378 was integrated: "4282-Backport-Pharo7-trying-to-add-an-ivar-to-UndefinedObject-crashes-the-VM-4017" Pull request url: https://github.com/pharo-project/pharo/pull/4378 Issue Url: https://pharo.fogbugz.com/f/cases/4282 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #658: 4365-Reintroduce-separator
by ci-pharo-ci-jenkins2＠inria.fr Aug. 22, 2019

Aug. 22, 2019

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

1 0

[Pharo 8.0] Build #657: CodeGenWeakClassVar
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2019

Aug. 21, 2019

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

1 0

[Pharo 8.0] Build #656: FormCanvas-has-wrong-lazy-initialization
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2019

Aug. 21, 2019

There is a new Pharo build available! The status of the build #656 was: FAILURE. The Pull Request #4390 was integrated: "FormCanvas-has-wrong-lazy-initialization" Pull request url: https://github.com/pharo-project/pharo/pull/4390 Issue Url: https://github.com/pharo-project/pharo/issues/FormCanvas Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Question on Behavior>>superclass:
by Jordi Delgado Aug. 21, 2019

Aug. 21, 2019

Hi, This example in the slides of Pharo MOOC, week 7, is broken in Pharo 7.0 (the variable newClass is not used, thus it has been removed): | behavior model | behavior := Behavior new. behavior superclass: Model. behavior setFormat: Model format. model := Model new. model primitiveChangeClassTo: behavior new. self assert: model class = behavior. self assert: model class superclass = Model. behavior compile: 'foo ^ 2'. self assert: model foo = 2. self should: [Model new foo] raise: MessageNotUnderstood (slide 14 in http://rmod-pharo-mooc.lille.inria.fr/MOOC/Slides/Week7/C019-W7S04-OtherRef…) The code is broken because there is no method Behavior>>classInstaller, and the message classInstaller is sent to self in Behavior>>superclass:. Adding a Behavior>>superclass2: to Pharo 7.0, copied from Pharo 6.1 Behavior>>superclass:, and using Behavior>>superclass2: in the example: | behavior model | behavior := Behavior new. behavior superclass2: Model. "<-------" behavior setFormat: Model format. model := Model new. model primitiveChangeClassTo: behavior new. self assert: model class = behavior. self assert: model class superclass = Model. behavior compile: 'foo ^ 2'. self assert: model foo = 2. self should: [Model new foo] raise: MessageNotUnderstood the code works again and the example is good. However, this is only an ugly workaround. Thus: I do not know why Behavior>>superclass: was changed in Pharo 7.0 but I guess it was not an accident. I assume it has to do with deep changes in the low level structure of the implementation of the language, having to do with slots, etc. I have browsed Pharo issues in github but I did not find anything related. Also, I'm not sure this problem qualifies as an "issue". So, my question is. Is it possible to easily adapt the example to the new Pharo 7.0? (with no silly workarounds, I mean). Thanks in advance and, as usual, apologies if the question is trivial and/or stupid. Bests, Jordi PS: Any Pharoer in CCCamp? -- Jordi Delgado Computer Science Department - Universitat PolitÃ¨cnica de Catalunya Campus Nord, Omega building, Office S115 c/Jordi Girona Salgado, 1-3 08034 Barcelona, Spain. Phone: +34.93.413.40.18 Public Key: https://pgp.mit.edu/pks/lookup?op=get&search=0xB7911543AD9E79A8

1 0

[Pharo 8.0] Build #655: 4272 Fix Spelling of Responsability
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2019

Aug. 21, 2019

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

1 0