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

[Pharo 7.0] Build #104: 22867-Add-a-comment-to-Metacello-cypress-recent-fix
by ci-pharo-ci-jenkins2＠inria.fr Jan. 8, 2019

Jan. 8, 2019

There is a new Pharo build available! The status of the build #104 was: SUCCESS. The Pull Request #2176 was integrated: "22867-Add-a-comment-to-Metacello-cypress-recent-fix" Pull request url: https://github.com/pharo-project/pharo/pull/2176 Issue Url: https://pharo.fogbugz.com/f/cases/22867 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Bad naming of libfreetype in latest Pharo vm windows 64bits
by Guillermo Polito Jan. 7, 2019

Jan. 7, 2019

Hi all, I'm trying the latest windows pharo VM 64bits (pharo-win-x86_64-201901051900-7a3c6b6.zip from http://files.pharo.org/vm/pharo-spur64/win/) to see how reproducible are the problems with freetype, athens and the bitblt. While in that I've found that libcairo does not load due to a bad naming of libfreetype. I had libfreetype.dll, and renaming it to libfreetype-6.dll made it loadable again. The 32bit windows VM that corresponds to the same commit, the freetype library file is also named libfreetype.dll but there it works. I've found that the specs for freetype for win64 in that commit are right: https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/7a3c6b642312bc2778fd… but maybe the default ones are used? https://github.com/OpenSmalltalk/opensmalltalk-vm/blob/7a3c6b642312bc2778fd… Does somebody know what else could be causing this? Tx, Guille

1 0

[Pharo 7.0] Build #103: 22865-Metacello-Baselines-using-the-copy-functionality-over-a-p
by ci-pharo-ci-jenkins2＠inria.fr Jan. 6, 2019

Jan. 6, 2019

There is a new Pharo build available! The status of the build #103 was: SUCCESS. The Pull Request #2173 was integrated: "22865-Metacello-Baselines-using-the-copy-functionality-over-a-p" Pull request url: https://github.com/pharo-project/pharo/pull/2173 Issue Url: https://pharo.fogbugz.com/f/cases/22865 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #102: 22493-Classes-after-Removing-traits-should-not-have-methods-from-TraitedClass
by ci-pharo-ci-jenkins2＠inria.fr Jan. 6, 2019

Jan. 6, 2019

There is a new Pharo build available! The status of the build #102 was: SUCCESS. The Pull Request #1847 was integrated: "22493-Classes-after-Removing-traits-should-not-have-methods-from-TraitedClass" Pull request url: https://github.com/pharo-project/pharo/pull/1847 Issue Url: https://pharo.fogbugz.com/f/cases/22493 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo-users] New book: Pharo with Style
by Esteban Maringolo Jan. 6, 2019

Jan. 6, 2019

I've read the whole booklet and I'm happy to follow most, if not all, the guidelines. Kent Beck's book was influential on this. I have a few remarks, though... Guideline 2.2 Typed variables should mention only existing or loadable types in the system. E.g selectFrom: aDate to: anotherDate and not selectFrom: aBeginningDate to: anEndDate (where Beginning and EndDate are not classes in the system) This affects guideline 2.3 because it says aBinaryBlock and there is no BinaryBlock class. I would also add another guideline here for the use of the 'as' preffix, e.g. asDate, asString, etc. where "as" means a different representation of receiver. E.g. asString is okay, while asShortString is not, because there is no ShortString class. Guideline 2.6 Should be "Number of" or "Count"? E.g. numberOfSomething or somethingCount? I don't like using "of" "with" or similar prepositions to name variables and classes. Guideline 3.2 #beSuprised would be better than #lookSurprised and follows a used convention of using #beSomething, e.g. #beBinary, #beReadOnly, etc. In the Guideline 5.6 the examples are the same. Regards! Esteban A. Maringolo El miÃ©., 2 ene. 2019 a las 2:33, Sean P. DeNigris via Pharo-dev (< pharo-dev(a)lists.pharo.org>) escribiÃ³: > Pharo Smalltalk Developers mailing list wrote > > Including what the method does, even when the code is fairly simple > > (OK, not getter / setter methods), is still useful. > > Yes, but... there is no free lunch. While there may be a benefit when the > code and comment are freshly written and in sync, they are duplication > which > smells whether code or comment and it is all too easy for the code to be > patched without updating the comment. Now that minor speedup turns into a > more significant slowdown when a user blindly follows the now-wrong > comment. > This possibility is made more likely be the fact that a stale comment will > not be picked up by the testing framework. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html > >

1 0

[Pharo 7.0] Build #101: 22843-Cannot-select-all-in-windows
by ci-pharo-ci-jenkins2＠inria.fr Jan. 5, 2019

Jan. 5, 2019

There is a new Pharo build available! The status of the build #101 was: SUCCESS. The Pull Request #2157 was integrated: "22843-Cannot-select-all-in-windows" Pull request url: https://github.com/pharo-project/pharo/pull/2157 Issue Url: https://pharo.fogbugz.com/f/cases/22843 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #100: 22864-SessionErrorHandlingTest-should-run-using-the-NonInteractiveUIManager
by ci-pharo-ci-jenkins2＠inria.fr Jan. 4, 2019

Jan. 4, 2019

There is a new Pharo build available! The status of the build #100 was: SUCCESS. The Pull Request #2169 was integrated: "22864-SessionErrorHandlingTest-should-run-using-the-NonInteractiveUIManager" Pull request url: https://github.com/pharo-project/pharo/pull/2169 Issue Url: https://pharo.fogbugz.com/f/cases/22864 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #99: 22863-Improve-Stability-of-Glamour-Tests
by ci-pharo-ci-jenkins2＠inria.fr Jan. 4, 2019

Jan. 4, 2019

There is a new Pharo build available! The status of the build #99 was: FAILURE. The Pull Request #2168 was integrated: "22863-Improve-Stability-of-Glamour-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/2168 Issue Url: https://pharo.fogbugz.com/f/cases/22863 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

libssh2 1.7.0 & 1.8.0
by Alistair Grant Jan. 4, 2019

Jan. 4, 2019

Hi Esteban, The VM is currently being built with libssh2 1.7.0, but this doesn't build on ARM v6 (Raspberry Pi) due to changes in openssl. libssh2 1.8.0, which was released in October 2016, builds and appears to function correctly (the VM crashes when attempting to commit from within Iceberg, but I think this is an unrelated problem). I've built and done some ad-hoc testing of libssh2 1.8.0 on linux 64 bit (Ubuntu 16.04) and haven't had any issues. What do you think of upgrading from libssh2 1.7.0 to 1.8.0? I don't know how close Pharo 7.0 is to release, but I expect this can wait until Pharo 8.0 if you prefer. For convenience: https://www.libssh2.org/ Thanks, Alistair

3 4

[Pharo 7.0] Build #98: Fixed issue 22688.
by ci-pharo-ci-jenkins2＠inria.fr Jan. 4, 2019

Jan. 4, 2019

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

1 0