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

Bad baseline practices
by Stephan Eggermont Jan. 15, 2019

Jan. 15, 2019

Iâm not sure why, but Iâve noticed baselines being changed to refer to patch versions for releases. Why are the old configuration problems repeated? Stephan

1 0

Managing of P7/P8
by Torsten Bergmann Jan. 15, 2019

Jan. 15, 2019

Hi, as Pharo 8 development started I wonder: 1. When will it be possible to already get a Pharo 8 latest image from ZeroConf. Because one requires ideally the latest image to contribute - no? Or should one search/download from the CI server for the time being (which would be cumbersome) 2. How will contributions still going to P7 handled regarding P8. Typically a bugfix for P7 should also go into the P8 image - no? But from the integration mails floating around I do not see this is happening. I would expect that a PR for Pharo 7 would also be merged into Pharo 8 branch. If not the images could easily diverge too much or done fixes for P7 will not be in P8. Thanks in advance for clarification! Bye T.

2 1

[Pharo 7.0] Build #122: 22894-Unecessary-dialogs-during-refactorings
by ci-pharo-ci-jenkins2＠inria.fr Jan. 15, 2019

Jan. 15, 2019

There is a new Pharo build available! The status of the build #122 was: FAILURE. The Pull Request #2235 was integrated: "22894-Unecessary-dialogs-during-refactorings" Pull request url: https://github.com/pharo-project/pharo/pull/2235 Issue Url: https://pharo.fogbugz.com/f/cases/22894 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #11: 2242-Sync-Pharo-7-and-8
by ci-pharo-ci-jenkins2＠inria.fr Jan. 15, 2019

Jan. 15, 2019

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

1 0

Availability of Smallapack in Pharo6.0
by Nicolas Cellier Jan. 14, 2019

Jan. 14, 2019

Hi, I announce the availability of Smallapack in Pharo6. The ConfigurationOfSmallapack is in http://www.squeaksource.com/MetacelloRepository and there is a copy in meta repo for Pharo 3/4/5/6. Currently, the ported version uses a derivative of OpalCompiler patched to handle method with 16+ arguments. External function calls have not been converted yet to UnifiedFFI, but the patched compiler rather has hook to compile legacy FFI. Though I did not install the hook to call FFI with more than 15 arguments, so there is at least 1 unit test failing (but not crashing). I have auto-re-generated all the source code for using UnifiedFFI formats, so the dependency on legacy FFI is not a necessity (apart for simplifying cross dialect maintenance). But I want to review the generated code method by method rather than filing it in blindly (the wrapper functions are also generated, and I might loose comments or improvments if I'm careless). Unfortunately, the state of diff tools in Pharo6, be it thru MC or worse than all, thru legacy change lists, does not enable such a large scale review, so I think that I will edit in Squeak and run in Pharo... Now that Smallapack supports Opal, there should be no major problem for porting to Pharo7, but I did not have time to try yet. A few more MC regressions, and the fact to forbid protocol beginning with a * was too serious a cross compatibility hurdle for me. But I'll come back to it, tools are generally better in ph7 than ph6. Stay tuned.

4 4

About resurrecting the RE package and plugin
by ducasse Jan. 14, 2019

Jan. 14, 2019

Hi I would really like to resurrect the REPlugin and its image side abstraction because I think that this is important to support Perl level regex since it will help people to reuse their knowledge. If you are interested in helping let us know. Stef

1 0

[ANN] New stable VMs promoted
by Esteban Lorenzano Jan. 14, 2019

Jan. 14, 2019

Hi, I just promoted the VM: 201901051900-7a3c6b6 (From Jan/05) As stable VMs for all platforms. Enjoyâ¦ and please report any problems ! Esteban

2 1

FFILibrary uniqueInstance
by Nicolas Cellier Jan. 14, 2019

Jan. 14, 2019

Hi all, I wanted to know if the moduleName was cached somewhere or recomputed at each function call... It seems to be recomputed. We could have a different scheme: moduleName is cached in a class inst var of FFILibrary. FFILibrary is then added to startup list and moduleName is reset when resuming on a different platform. instance side moduleName calls class side moduleName. Or moduleName becomes an inst var, set during uniqueInstance construction, and uniqueInstance is nilled out when resuming. What do you think?

5 4

Development process: testing the GUI
by Nicolas Cellier Jan. 14, 2019

Jan. 14, 2019

Hi all, Pharo team is attaching great care in securing and improving the development process, notably by promoting usage of tests and continuous integration. I think a very good job is already done in the libraries provided by Pharo. But sometimes I encounter more hickups with the development tools themselves. So I wonder: does this apply to the GUI yet? This is a difficult area, but nowadays this exists elsewhere. For example, with Elm and Elmer ( https://medium.com/@brian.watkins/test-driving-elm-with-elmer-649e2e7e02a8) TDD can be applied on UI, providing both a formal specification and non regression tests. Do we have something similar? Don't we wish having something similar?

3 3

Esteban's ChangeLog week of 7 January 2019
by estebanlm＠gmail.com Jan. 14, 2019

Jan. 14, 2019

Hello! This is my weekly ChangeLog, from 7 January 2019 to 13 January 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=7/1/2019&to=13/1/2019 ChangeLog ========= 11 January 2019: ---------------- * Finally fixed bootstrap issues related to Pharo8.0 development. Now we are ready to go :) Issues fixed: * [https://github.com/pharo-project/pharo/pull/2214](https://github.com/pharo-… * [https://github.com/pharo-project/pharo/issues/2212](https://github.com/phar… * [https://github.com/pharo-project/pharo/issues/2129](https://github.com/phar… * [https://github.com/pharo-project/pharo/issues/2211](https://github.com/phar… * [https://github.com/pharo-project/pharo/issues/2130](https://github.com/phar… 9 January 2019: --------------- * I've been working on release Pharo7.0 as soon as possible. For that, Pharo8.0 development needs to be in place and there were some errors on the bootstrap. I'm working on those: * [2129](https://github.com/pharo-project/pharo/issues/2129) * [2130](https://github.com/pharo-project/pharo/issues/2130) Both are kind of related, since it depends on how to take correctly the working branch. Anyway... not finished, but almost :) cheers! Esteban

1 0