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

[Ann] Some new iceberg videos

by Guillermo Polito

Hi all, This time (just before releasing a new version of iceberg) I wanted to share some videos with you. Feedback is welcome. !! How to contribute to Iceberg https://youtu.be/yGr5HvVWM0M This video shows how to contribute to iceberg. For this, you should update your iceberg installation and then just do a pull request. This means that you need to start by forking https://github.com/pharo-vcs/iceberg - Path 1: Clone and pull (easy) - Clone your fork - Checkout the latest development branch (e.g., dev-0.7) - Pull from pharo-vcs/iceberg This path does not always work, as this is kind of self-brain surgery. Iceberg is updating itself. If this does not work, go to path 2 - Path 2: Install from scratch (if Path 1 does not work) - Use the script in the README file to unload and reinstall iceberg - Make sure you use the latest development branch in the Metacello script (e.g., dev-0.7) - Clone your fork and checkout the development branch Once you have the correct version, you can load the tests by loading the development group of the baseline. !! Basic Branching and Merging https://youtu.be/c0IgIT2s6Js This video shows in a simple example how to branch, merge and checkout different commits. In this video we first create a new class with a method, then we create another branch and force a conflict. We resolve the conflict during merge. In the middle, bonus feature, we checked out a commit and stayed in Detached HEAD for a while ;) !! Loading a baseline from your repository https://youtu.be/brUHEOr-p_E This video shows how to load a baseline from Iceberg's UI. We clone an existing project, see it is "Not loaded" and use Metacello plugin to load the default group. Enjoy, Guille PS: Tomorrow I'll answer the threads about Iceberg that were going around here in the mailing list. I was running today.

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Marcus Denker

> On 23 May 2018, at 13:53, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 23 May 2018, at 13:47, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >> >>> On 23 May 2018, at 13:30, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >>> >>> 2018-05-23 13:20 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: >>>> Marcus Denker-4 wrote >>>>> method := Smalltalk compiler >>>>> environment: environment; >>>>> compile: 'tt ^MyClassâ. >>>> >>>> Awesome! Is it possible to override a global from /within/ a method (e.g. in >>>> a test)? >>> >>> I think at the class level by manipulating that class compiler >> >> Yes. You can override the class side method: >> >> in Behaviour, it is defined as >> >> compiler >> "Answer a compiler appropriate for source methods of this class." >> >> ^self compilerClass new >> environment: self environment; >> class: self >> >> so you can just >> >> compiler >> âChange the compiler environment " >> >> ^super compiler >> environment: self myEnvironment >> >> >> and it should work. > > Here we can see, too, that we need to do more work. In Behaviour: > > environment > "Return the environment in which the receiver is visible" > ^Smalltalk globals > > For classes to automatically compile with the environment they are in, we somehow need to return here > that environmentâ¦ This is already correct (Class overrides it, all classes have the ivar environment correctly set) Marcus

May 23, 2018

[Pharo 7.0-dev] Build #941: 21938-FileDoesNotExistException-defaultAction-has-some-glitches

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

There is a new Pharo build available! The status of the build #941 was: FAILURE. The Pull Request #1393 was integrated: "21938-FileDoesNotExistException-defaultAction-has-some-glitches" Pull request url: https://github.com/pharo-project/pharo/pull/1393 Issue Url: https://pharo.fogbugz.com/f/cases/21938 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 23, 2018

[Pharo 7.0-dev] Build #940: 21952-FileSystemStoresignalFileDoesNotExist-creates-bad-exception

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

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

May 23, 2018

[Pharo 7.0-dev] Build #939: 16076-make-environment-work-for-Opal

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

There is a new Pharo build available! The status of the build #939 was: FAILURE. The Pull Request #1406 was integrated: "16076-make-environment-work-for-Opal" Pull request url: https://github.com/pharo-project/pharo/pull/1406 Issue Url: https://pharo.fogbugz.com/f/cases/16076 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Sean P. DeNigris

Marcus Denker-4 wrote > indeed.. I still believe that we should late-bind global access :-) I'll keep +1-ing every time you mention this ha ha ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Marcus Denker

> On 23 May 2018, at 13:47, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > >> On 23 May 2018, at 13:30, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: >> >> 2018-05-23 13:20 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: >>> Marcus Denker-4 wrote >>>> method := Smalltalk compiler >>>> environment: environment; >>>> compile: 'tt ^MyClassâ. >>> >>> Awesome! Is it possible to override a global from /within/ a method (e.g. in >>> a test)? >> >> I think at the class level by manipulating that class compiler > > Yes. You can override the class side method: > > in Behaviour, it is defined as > > compiler > "Answer a compiler appropriate for source methods of this class." > > ^self compilerClass new > environment: self environment; > class: self > > so you can just > > compiler > âChange the compiler environment " > > ^super compiler > environment: self myEnvironment > > > and it should work. Here we can see, too, that we need to do more work. In Behaviour: environment "Return the environment in which the receiver is visible" ^Smalltalk globals For classes to automatically compile with the environment they are in, we somehow need to return here that environmentâ¦ Marcus

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Marcus Denker

> On 23 May 2018, at 13:30, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > 2018-05-23 13:20 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: >> Marcus Denker-4 wrote >>> method := Smalltalk compiler >>> environment: environment; >>> compile: 'tt ^MyClassâ. >> >> Awesome! Is it possible to override a global from /within/ a method (e.g. in >> a test)? > > I think at the class level by manipulating that class compiler Yes. You can override the class side method: in Behaviour, it is defined as compiler "Answer a compiler appropriate for source methods of this class." ^self compilerClass new environment: self environment; class: self so you can just compiler âChange the compiler environment " ^super compiler environment: self myEnvironment and it should work. an a per method bases, we can only manipulate the compiler via Pragmas to set options: <compilerOptions: #(+ optionInlineTimesRepeat)> for example. > (and > forcing a method recompile...) > indeed.. I still believe that we should late-bind global access :-) Marcus

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Thierry Goubier

2018-05-23 13:20 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com>: > Marcus Denker-4 wrote >> method := Smalltalk compiler >> environment: environment; >> compile: 'tt ^MyClassâ. > > Awesome! Is it possible to override a global from /within/ a method (e.g. in > a test)? I think at the class level by manipulating that class compiler (and forcing a method recompile...) Thierry > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

May 23, 2018

Re: [Pharo-dev] [Compiler] #bindings: improvement: Global shadowing

by Sean P. DeNigris

Marcus Denker-4 wrote > method := Smalltalk compiler > environment: environment; > compile: 'tt ^MyClassâ. Awesome! Is it possible to override a global from /within/ a method (e.g. in a test)? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

May 23, 2018