April 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #790: 21749-Removing-Override-support-from-RPackage
by ci-pharo-ci-jenkins2＠inria.fr April 20, 2018

April 20, 2018

There is a new Pharo build available! The status of the build #790 was: SUCCESS. The Pull Request #1236 was integrated: "21749-Removing-Override-support-from-RPackage" Pull request url: https://github.com/pharo-project/pharo/pull/1236 Issue Url: https://pharo.fogbugz.com/f/cases/21749 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #789: 21741-subclasslayoutslotsclassVariablespoolDictionaries-should-receive-a-collection-of-symbols
by ci-pharo-ci-jenkins2＠inria.fr April 20, 2018

April 20, 2018

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

1 0

[Pharo 7.0-dev] Build #788: 21747-BlockClosure-sourceCode-tab-should-provide-self-binding
by ci-pharo-ci-jenkins2＠inria.fr April 20, 2018

April 20, 2018

There is a new Pharo build available! The status of the build #788 was: SUCCESS. The Pull Request #1232 was integrated: "21747-BlockClosure-sourceCode-tab-should-provide-self-binding" Pull request url: https://github.com/pharo-project/pharo/pull/1232 Issue Url: https://pharo.fogbugz.com/f/cases/21747 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Small lint cleanups for Zodiac
by Torsten Bergmann April 20, 2018

April 20, 2018

Hi Sven, attached some small lint cleanups for Zodiac as I was not able to commit to Zodiac on SThub. Changes mentioned below. This was done in Pharo 7 but based on latest MCZ's. Thx T. ------------------------------------------------------------------------------ Name: Zodiac-Core-TorstenBergmann.48 Author: TorstenBergmann Time: 4 April 2018, 7:45:15.792684 am UUID: 2c097b10-6125-0d00-ae7c-de9200a97a05 Ancestors: Zodiac-Core-SvenVanCaekenberghe.47 use common "initialization" category to prevent lint problems in Pharo 7 ------------------------------------------------------------------------------ Name: Zodiac-Tests-TorstenBergmann.20 Author: TorstenBergmann Time: 4 April 2018, 7:51:47.289684 am UUID: 54ced027-6125-0d00-ae7d-4b5100a97a05 Ancestors: Zodiac-Tests-SvenVanCaekenberghe.19 add comment for ZdcByteArrayManagerTests ------------------------------------------------------------------------------ Name: Zodiac-Tests-TorstenBergmann.21 Author: TorstenBergmann Time: 4 April 2018, 8:08:38.372684 am UUID: 4cb51464-6125-0d00-ae7e-d1a000a97a05 Ancestors: Zodiac-Tests-TorstenBergmann.20 Lint cleanup: use #assert:equals: and remove unnecessary nots

2 1

[Pharo 7.0-dev] Build #787: 21652-Smalltalk-allClassesAndTraits-duplicates-all-traits
by ci-pharo-ci-jenkins2＠inria.fr April 20, 2018

April 20, 2018

There is a new Pharo build available! The status of the build #787 was: SUCCESS. The Pull Request #1227 was integrated: "21652-Smalltalk-allClassesAndTraits-duplicates-all-traits" Pull request url: https://github.com/pharo-project/pharo/pull/1227 Issue Url: https://pharo.fogbugz.com/f/cases/21652 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #786: 21745-Trait-new-should-raise-error-instead-of-VM-crash
by ci-pharo-ci-jenkins2＠inria.fr April 20, 2018

April 20, 2018

There is a new Pharo build available! The status of the build #786 was: SUCCESS. The Pull Request #1229 was integrated: "21745-Trait-new-should-raise-error-instead-of-VM-crash" Pull request url: https://github.com/pharo-project/pharo/pull/1229 Issue Url: https://pharo.fogbugz.com/f/cases/21745 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #785: 21733 Categorize methods in FontChoosers4
by ci-pharo-ci-jenkins2＠inria.fr April 20, 2018

April 20, 2018

There is a new Pharo build available! The status of the build #785 was: SUCCESS. The Pull Request #1219 was integrated: "21733 Categorize methods in FontChoosers4" Pull request url: https://github.com/pharo-project/pharo/pull/1219 Issue Url: https://pharo.fogbugz.com/f/cases/21733 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #784: 21735 Improve AnnouncerTest
by ci-pharo-ci-jenkins2＠inria.fr April 20, 2018

April 20, 2018

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

1 0

Changed #atEnd primitive - #atEnd vs #next returning nil
by Sven Van Caekenberghe April 20, 2018

April 20, 2018

Somehow, somewhere there was a change to the implementation of the primitive called by some streams' #atEnd. IIRC, someone said it is implemented as 'remaining size being zero' and some virtual unix files like /dev/random are zero sized. Now, all kinds of changes are being done image size to work around this. I am a strong believer in simple, real (i.e. infinite) streams, but I am not sure we are doing the right thing here. Point is, I am not sure #next returning nil is official and universal. Consider the comments: Stream>>#next "Answer the next object accessible by the receiver." ReadStream>>#next "Primitive. Answer the next object in the Stream represented by the receiver. Fail if the collection of this stream is not an Array or a String. Fail if the stream is positioned at its end, or if the position is out of bounds in the collection. Optional. See Object documentation whatIsAPrimitive." Note how there is no talk about returning nil ! I think we should discuss about this first. Was the low level change really correct and the right thing to do ? Note also that a Guille introduced something new, #closed which is related to the difference between having no more elements (maybe right now, like an open network stream) and never ever being able to produce more data. Sven

9 62

DelayScheduler cleanup & Bootstrap
by Ben Coman April 20, 2018

April 20, 2018

I am doing a pass to cleanup the DelayScheduler hierarchy. I'll be refactoring of the hierarchy to aid code understanding and eliminate redundant instance variables from the original code. The target structure is.... DelayNullScheduler -- minimum interface to avoid errors in rest of system (6 empty methods) |__DelayBasicScheduler -- fully working sans race protection (equivalent to Courageous scheduler) |__DelaySpinScheduler -- plus race protection Can someone advise how/where the Bootstrap loads Delay and the DelaySchedulers? where the invocation of Delay_class>>#initialize selects the delay scheduler. I need to determine whether during transition the Bootstrap might need to temporarily hop to a different scheduler, and how to provide the new structure in the Image for operational testing before switching. cheers -ben

3 4