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

[Pharo 9.0] Build #242: Integrate Heuristic Completion v3.0.2
by ci-pharo-ci-jenkins2＠inria.fr April 16, 2020

April 16, 2020

There is a new Pharo build available! The status of the build #242 was: SUCCESS. The Pull Request #6187 was integrated: "Integrate Heuristic Completion v3.0.2" Pull request url: https://github.com/pharo-project/pharo/pull/6187 Issue Url: https://github.com/pharo-project/pharo/issues/fix/integratecompletion301 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #241: Try fix #6021
by ci-pharo-ci-jenkins2＠inria.fr April 16, 2020

April 16, 2020

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

1 0

[Pharo 9.0] Build #240: Fix Warning defaultAction
by ci-pharo-ci-jenkins2＠inria.fr April 16, 2020

April 16, 2020

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

1 0

looking for input for a lecture on TDD and XtremeTDD
by StÃ©phane Ducasse April 15, 2020

April 15, 2020

Hello I would like to build a lecture around TDD and XtremeTDD (coding in the debugger). Iâm looking around to see if someone already did such a lecture. S. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

4 4

[Pharo 9.0] Build #239: CompilerCleanup-hasIncompleteIdentifier
by ci-pharo-ci-jenkins2＠inria.fr April 15, 2020

April 15, 2020

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

1 0

[Pharo 9.0] Build #238: Improve Spacetally perfs and clean code
by ci-pharo-ci-jenkins2＠inria.fr April 15, 2020

April 15, 2020

There is a new Pharo build available! The status of the build #238 was: FAILURE. The Pull Request #6177 was integrated: "Improve Spacetally perfs and clean code" Pull request url: https://github.com/pharo-project/pharo/pull/6177 Issue Url: https://github.com/pharo-project/pharo/issues/improveSpaceTallyPerfs Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #237: Pharo project is not the Pharo Launcher project
by ci-pharo-ci-jenkins2＠inria.fr April 15, 2020

April 15, 2020

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

1 0

[Vm-dev] Pony for Pharo VM (typo fix)
by Shaping April 15, 2020

April 15, 2020

Hi Ken. Not to discourage people, but I have not seen cases where a "strong" type system would be able to scale for _real_ Smalltalk applications. Youâre right. It doesn't. I'm not suggesting that. The type safety is not for app-level Smalltalk development. It's for building the VM only. I want to use the Pony concurrency model at the Smalltalk level. Thatâs the gist of it. Otherwise, I want a Smalltalk, not a statically compiled language. Six ref-caps explicitly represent Ponyâs concurrency model in code. They are essentially type qualifiers related specifically to concurrency. The plan is to reduce, if possible, the number of ref-caps the programmer must explicitly use/place in the code when coding a state-machine in Smalltalk, without producing a toy or straightjacket (without making it too simple or too rigid). This may require implementing the VM more as a change to (fork of) Pony instead of using Pony to implement the VM. Iâm not sure yet. The six ref-cap ideas for sharing data reliably between actors are not hard to grasp, but they take some getting used to, and involve some mental load. I don't want that much (concurrency-related or any other) implementation detail in the domain layer, much in the same vein as: I donât use Forth because I donât want to see stack acrobatics (ROTs and DUPs, etc.) amidst domain-level state-changes (FirePhotonTorpedo). Itâs distracting. It dilutes focus on the domain work/layer, and tends to cause mistakes there. The programmerâs domain logic and the concurrency-integrity provided by the ref-caps are different layers of thought and structure. The ref-caps are, however, mixed freely with domain logic in current Pony code. I think thatâs a mistake. But thatâs how it is now. I think of this layer mixing as an intermediate design stage of Pony. I want to abstract-out some or all ref-caps as the VM is built. Pony language is not the remarkable thing here. I see it as a better C or better Rust. Itâs very good (as Algol-60-ish-looking crap-syntaxes go), but thatâs not what this is about. Itâs about the actor programming, the concurrency model, and the guarantees given by use of the ref-caps. We would still obviously need to respect the Pony compilerâs determination of where ref-cap use is correct or not. Your Pony program wonât compile if you donât use the ref-caps correctly, and you donât get the guarantees or a running program without the compile. Much easier, therefore, might be to go the other way by changing Pony to support dynamic types without violating the invariants that allow the ref-caps (under the hood, abstracted out) to make the concurrency guarantees. Work Smalltalk dynamism into Pony, instead of building a Smalltalk VM with Pony. Shaping "Rational numbers" (1/2) + (1/3) + (1/6). "--> 1 " "Complex numbers" [ :n | n * n] value: (-4 sqrt). "--> -4 " "BigNums" 111 factorial. " --> 1762952551090244663872161047107075788761409536026565516041574063347346955087248316436555574598462315773196047662837978913145847497199871623320096254145331200000000000000000000000000 " Just this is hugely complex to model in a "type safe" language. Add metaprogramming (e.g. #doesNotUnderstand:), source level debugging of live stacks and GC of large object spaces and you have a very large (space) and very slow (interlocking cache granularity) interpreter. Please prove me wrong. $0.02, -KenD

2 2

[Pharo 9.0] Build #236: Fix 6160 Cleanup two tests in BlockClosureTest
by ci-pharo-ci-jenkins2＠inria.fr April 14, 2020

April 14, 2020

There is a new Pharo build available! The status of the build #236 was: FAILURE. The Pull Request #6178 was integrated: "Fix 6160 Cleanup two tests in BlockClosureTest" Pull request url: https://github.com/pharo-project/pharo/pull/6178 Issue Url: https://github.com/pharo-project/pharo/issues/6160 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #235: Review Spotter preview logic of SpEntry
by ci-pharo-ci-jenkins2＠inria.fr April 14, 2020

April 14, 2020

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

1 0