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

[ANN] 900 pull requests closed for Pharo7!
by Marcus Denker Feb. 24, 2018

Feb. 24, 2018

Hi, March 11, we passed 800. Today (just now) we closed 900 full requests! https://github.com/pharo-project/pharo/pulls <https://github.com/pharo-project/pharo/pulls> Marcus

4 3

[update 6.0] #60535
by Marcus Denker Feb. 24, 2018

Feb. 24, 2018

â¦ CI just started to build: 60535 ----- 21236 Sometimes the debugger opens with the context one off https://pharo.fogbugz.com/f/cases/21236 21324 Missing "Browse receiver" feature in the debugger https://pharo.fogbugz.com/f/cases/21324

2 1

#valueWithPossibleArgs:, #valueWithEnoughArguments:, and #cull:
by Stefan Marr Feb. 24, 2018

Feb. 24, 2018

Hi: I am trying to understand the different between and perhaps origin of BlockClosure>>#valueWithPossibleArgs: and BlockClosure>>#valueWithEnoughArguments: I am trying to decide which of the two I need for SOMns. The first one has seen more recent changes, when looking at the Pharo 6.1 download: valueWithPossibleArgs: anArray â> 2/12/2017 StephaneDucasse valueWithEnoughArguments: anArray â> 3/11/2001 nk While they have rather different implementations, they seem to behave identically, as far as I could tell using the following example: blocks := { [ { } ]. [:a | { a } ]. [:a :b | { a. b } ]. [:a :b :c | { a. b. c } ] }. blocks collect: [:b | b valueWithPossibleArgs: {1}]. blocks collect: [:b | b valueWithPossibleArgs: {1. 2. 3}]. blocks collect: [:b | b valueWithEnoughArguments: {1}]. blocks collect: [:b | b valueWithEnoughArguments: {1. 2. 3}]. I was also wondering how they relate to #cull:* One of the major differences seems to be that valueWithP* and valueWithE* are both injecting nil for absent arguments, while normal #value* and #cull* methods signal an error. Is there a specific use case why one wouldnât want to be strict here as well, but instead inject nils? Any comments or pointer appreciated. Thanks Stefan -- Stefan Marr School of Computing, University of Kent http://stefan-marr.de/research/

9 16

[Pharo 7.0-dev] Build #601: 21374-Cancel-if-there-are-unsolved-depencies-during-bootstrap
by ci-pharo-ci-jenkins2＠inria.fr Feb. 23, 2018

Feb. 23, 2018

There is a new Pharo build available! The status of the build #601 was: FAILURE. The Pull Request #918 was integrated: "21374-Cancel-if-there-are-unsolved-depencies-during-bootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/918 Issue Url: https://pharo.fogbugz.com/f/cases/21374 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #600: 21324-Missing-Browse-receiver-feature-in-the-debugger
by ci-pharo-ci-jenkins2＠inria.fr Feb. 23, 2018

Feb. 23, 2018

There is a new Pharo build available! The status of the build #600 was: SUCCESS. The Pull Request #945 was integrated: "21324-Missing-Browse-receiver-feature-in-the-debugger" Pull request url: https://github.com/pharo-project/pharo/pull/945 Issue Url: https://pharo.fogbugz.com/f/cases/21324 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #599: 21320-externalName-still-exists-in-class-Class
by ci-pharo-ci-jenkins2＠inria.fr Feb. 23, 2018

Feb. 23, 2018

There is a new Pharo build available! The status of the build #599 was: SUCCESS. The Pull Request #947 was integrated: "21320-externalName-still-exists-in-class-Class" Pull request url: https://github.com/pharo-project/pharo/pull/947 Issue Url: https://pharo.fogbugz.com/f/cases/21320 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #598: 21399 Use category "utilities" instead of "utils" in GTSUnitDebuggerSmokeTest, GoferOperationTest, MonticelloRepositoryBrowser and NativeArrayTest
by ci-pharo-ci-jenkins2＠inria.fr Feb. 23, 2018

Feb. 23, 2018

There is a new Pharo build available! The status of the build #598 was: SUCCESS. The Pull Request #942 was integrated: "21399 Use category "utilities" instead of "utils" in GTSUnitDebuggerSmokeTest, GoferOperationTest, MonticelloRepositoryBrowser and NativeArrayTest" Pull request url: https://github.com/pharo-project/pharo/pull/942 Issue Url: https://pharo.fogbugz.com/f/cases/21399 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[update 6.0] #60534
by Marcus Denker Feb. 23, 2018

Feb. 23, 2018

â¦ will be the next build (ci is starting) 60534 ----- 21345 Backport World Menu priority https://pharo.fogbugz.com/f/cases/21345

1 0

[Pharo 7.0-dev] Build #597: 21395 Remove obsolete temps in ObsoleteTest
by ci-pharo-ci-jenkins2＠inria.fr Feb. 23, 2018

Feb. 23, 2018

There is a new Pharo build available! The status of the build #597 was: SUCCESS. The Pull Request #938 was integrated: "21395 Remove obsolete temps in ObsoleteTest" Pull request url: https://github.com/pharo-project/pharo/pull/938 Issue Url: https://pharo.fogbugz.com/f/cases/21395 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #596: 21398 Use category "utilities" instead of "utils" in MBConfigurationInfo MBInfo MBPackageInfo MBProjectInfo
by ci-pharo-ci-jenkins2＠inria.fr Feb. 23, 2018

Feb. 23, 2018

There is a new Pharo build available! The status of the build #596 was: SUCCESS. The Pull Request #941 was integrated: "21398 Use category "utilities" instead of "utils" in MBConfigurationInfo MBInfo MBPackageInfo MBProjectInfo" Pull request url: https://github.com/pharo-project/pharo/pull/941 Issue Url: https://pharo.fogbugz.com/f/cases/21398 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0