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

[Pharo 8.0] Build #990: Replace-assert-equals-from-Morphic

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #990 was: SUCCESS. The Pull Request #5171 was integrated: "Replace-assert-equals-from-Morphic" Pull request url: https://github.com/pharo-project/pharo/pull/5171 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 19, 2019

[Pharo 8.0] Build #989: Replace-assert-equals-from-packages-starting-with-J-and-K

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #989 was: SUCCESS. The Pull Request #5170 was integrated: "Replace-assert-equals-from-packages-starting-with-J-and-K" Pull request url: https://github.com/pharo-project/pharo/pull/5170 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 19, 2019

Pharo Techtalk Nov 21

by Marcus Denker

Hi, Next techtalk will be *this* week (Nov 21): Topic: Discussion around Contributing to Pharo8 The idea is to discuss on Discord and may do some examples liveâ¦ Calendar entry: https://association.pharo.org/event-3419546 (sorry for the late announceâ¦ )

Nov. 19, 2019

[Pharo 8.0] Build #988: Replace-assert-equals-from-packages-starting-with-H

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #988 was: FAILURE. The Pull Request #5169 was integrated: "Replace-assert-equals-from-packages-starting-with-H" Pull request url: https://github.com/pharo-project/pharo/pull/5169 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 19, 2019

Re: [Pharo-dev] AbstractEnvironmentTestCase

by Sven Van Caekenberghe

> On 19 Nov 2019, at 12:27, ducasse <stepharo(a)netcourrier.com> wrote: > > > >> On 19 Nov 2019, at 11:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Hi, >> >> AbstractEnvironmentTestCase exists only in Pharo 8, tracking this with STON (from changes in Pharo 8) gives me tests that can no longer be loaded in Pharo 7 (or versions before that). >> >> At least AbstractEnvironmentTestCase should be back ported to Pharo 7. >> >> Apart from that, I don't think this is a good change (since it breaks backwards compatibility >> too much). > > I do not agree. Well, external code cannot write tests that confirms to the requirements of both versions. >> Why do all Smalltalk>>#at: references have to be removed ? The way I see it, Smalltalk>>#at: could be rewritten to dynamically use a different environment, if that is set up earlier, using a DynamicVariable. Similarly, #asClass could be implemented to follow the same path. > > Because if one day we want to have modules and environment better to have a system that does not point to > global variables. > We should not refer to global variables. But eventually, the reference has to be resolved and it has a name. I am familiar with packages in common lisp, is it like that ? Is there a document that describes these issues more clearly ? The plan going forward ? > Stef > > >> >> Or am I wrong ? >> >> Sven

Nov. 19, 2019

Re: [Pharo-dev] AbstractEnvironmentTestCase

by ducasse

> On 19 Nov 2019, at 11:57, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi, > > AbstractEnvironmentTestCase exists only in Pharo 8, tracking this with STON (from changes in Pharo 8) gives me tests that can no longer be loaded in Pharo 7 (or versions before that). > > At least AbstractEnvironmentTestCase should be back ported to Pharo 7. > > Apart from that, I don't think this is a good change (since it breaks backwards compatibility > too much). I do not agree. > Why do all Smalltalk>>#at: references have to be removed ? The way I see it, Smalltalk>>#at: could be rewritten to dynamically use a different environment, if that is set up earlier, using a DynamicVariable. Similarly, #asClass could be implemented to follow the same path. Because if one day we want to have modules and environment better to have a system that does not point to global variables. We should not refer to global variables. Stef > > Or am I wrong ? > > Sven > > >

Nov. 19, 2019

AbstractEnvironmentTestCase

by Sven Van Caekenberghe

Hi, AbstractEnvironmentTestCase exists only in Pharo 8, tracking this with STON (from changes in Pharo 8) gives me tests that can no longer be loaded in Pharo 7 (or versions before that). At least AbstractEnvironmentTestCase should be back ported to Pharo 7. Apart from that, I don't think this is a good change (since it breaks backwards compatibility too much). Why do all Smalltalk>>#at: references have to be removed ? The way I see it, Smalltalk>>#at: could be rewritten to dynamically use a different environment, if that is set up earlier, using a DynamicVariable. Similarly, #asClass could be implemented to follow the same path. Or am I wrong ? Sven

Nov. 19, 2019

[Pharo 8.0] Build #987: Replace-assert-equals-from-packages-starting-with-F

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #987 was: SUCCESS. The Pull Request #5160 was integrated: "Replace-assert-equals-from-packages-starting-with-F" Pull request url: https://github.com/pharo-project/pharo/pull/5160 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 19, 2019

[Pharo 8.0] Build #986: CompilerNilCompiler

by ci-pharo-ci-jenkins2＠inria.fr

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

Nov. 19, 2019

[Pharo 8.0] Build #985: Replace-assert-equals-from-Epicea

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #985 was: SUCCESS. The Pull Request #5159 was integrated: "Replace-assert-equals-from-Epicea" Pull request url: https://github.com/pharo-project/pharo/pull/5159 Issue Url: https://github.com/pharo-project/pharo/issues/Replace Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 18, 2019