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

[Pharo 7.0-dev] Build #776: 21722-Small-Cleanup-Syntax-highlighting-remove-a-reference-to-SHParserST80
by ci-pharo-ci-jenkins2＠inria.fr April 17, 2018

April 17, 2018

There is a new Pharo build available! The status of the build #776 was: SUCCESS. The Pull Request #1210 was integrated: "21722-Small-Cleanup-Syntax-highlighting-remove-a-reference-to-SHParserST80" Pull request url: https://github.com/pharo-project/pharo/pull/1210 Issue Url: https://pharo.fogbugz.com/f/cases/21722 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pavel's ChangeLog week of 2018-02-05
by Pavel Krivanek April 17, 2018

April 17, 2018

Hi, among other less interesting things, I spent some time on existing PosixSharedMemory project. It is a UFFI binding for the LibC methods that provide support for the memory allocation between several separate processes. I significantly improved the performance by implementing the block access. Writing of 10MB byte array takes about 1 millisecond, reading of it from other image took me about 4 milliseconds. While serialization with Fuel is very fast, it opens interesting possibilities. To have a shared memory without synchronization tools is not very useful so I wrote a basic UFFI interface for the POSIX named semaphores. They are quite easy to use and work nicely with Pharo. The VM can all wait on the semaphore or it can check the status of it periodically in an image thread. It has two small disadvantages. It requires to dynamically link the next library (pthread) and they must be cleaned manually. I plan to look at System V alternative in future. Now we should write a nice framework for inter-image communication on top of it or/and adopt Seamless for it ;-) Cheers, -- Pavel

6 10

[Pharo 7.0-dev] Build #775: Revert "21429-Watchpoints-should-be-cleaned-when-system-changed"
by ci-pharo-ci-jenkins2＠inria.fr April 17, 2018

April 17, 2018

There is a new Pharo build available! The status of the build #775 was: SUCCESS. The Pull Request #1209 was integrated: "Revert "21429-Watchpoints-should-be-cleaned-when-system-changed"" Pull request url: https://github.com/pharo-project/pharo/pull/1209 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

[Pharo 7.0-dev] Build #774: 21429-Watchpoints-should-be-cleaned-when-system-changed
by ci-pharo-ci-jenkins2＠inria.fr April 17, 2018

April 17, 2018

There is a new Pharo build available! The status of the build #774 was: FAILURE. The Pull Request #1162 was integrated: "21429-Watchpoints-should-be-cleaned-when-system-changed" Pull request url: https://github.com/pharo-project/pharo/pull/1162 Issue Url: https://pharo.fogbugz.com/f/cases/21429 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #773: 21523-package-ReflectionMirrors-Primitives-needs-to-be-moved-to-the-BaselineOfPharoBootstrap
by ci-pharo-ci-jenkins2＠inria.fr April 17, 2018

April 17, 2018

There is a new Pharo build available! The status of the build #773 was: SUCCESS. The Pull Request #1051 was integrated: "21523-package-ReflectionMirrors-Primitives-needs-to-be-moved-to-the-BaselineOfPharoBootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/1051 Issue Url: https://pharo.fogbugz.com/f/cases/21523 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #772: 21715-When-asking-for-the-context-in-a-after-node-on-a-method-return-context-of-method-not-the-ensure-block
by ci-pharo-ci-jenkins2＠inria.fr April 17, 2018

April 17, 2018

There is a new Pharo build available! The status of the build #772 was: SUCCESS. The Pull Request #1205 was integrated: "21715-When-asking-for-the-context-in-a-after-node-on-a-method-return-context-of-method-not-the-ensure-block" Pull request url: https://github.com/pharo-project/pharo/pull/1205 Issue Url: https://pharo.fogbugz.com/f/cases/21715 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #771: 21716 File size should be in accessing protocol
by ci-pharo-ci-jenkins2＠inria.fr April 17, 2018

April 17, 2018

There is a new Pharo build available! The status of the build #771 was: SUCCESS. The Pull Request #1207 was integrated: "21716 File size should be in accessing protocol" Pull request url: https://github.com/pharo-project/pharo/pull/1207 Issue Url: https://pharo.fogbugz.com/f/cases/21716 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 9 April 2018
by estebanlm＠gmail.com April 16, 2018

April 16, 2018

Hello! This is my weekly ChangeLog, from 9 April 2018 to 15 April 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=9/4/2018&to=15/4/2018 ChangeLog ========= 13 April 2018: -------------- * I just promoted new VMs as stable. This are the builds corresponding to: 201804122226 (07c6dc3) this passed the build tests so 'it should' be ok :) 12 April 2018: -------------- * on iceberg, closed [https://github.com/pharo-vcs/iceberg/issues/628](https://github.com/pharo-v… to fix a compatibility error. 11 April 2018: -------------- * Ok, while waiting for the Pharo CI to comeback to life (so I can release Iceberg 0.7), I managed to fix a small issue it was annoying me since a lot of time: [https://github.com/estebanlm/opensmalltalk-vm/issues/4](https://github.com/… . This is because I still want to produce real headlesss VMs so I need to slowly move things in that direction. Anyway... since this was an image-side problem more than a VM problem, I have a [case: 21688](https://pharo.fogbugz.com/f/cases/21688) in Pharo issue tracker and a [PR](https://github.com/pharo-project/pharo/pull/1191) 9 April 2018: ------------- * I just finished iceberg [issue 594](https://github.com/pharo-vcs/iceberg/issues/594) : new Iceberg 0.7 (to be released) to load also on Pharo 6.1. cheers! Esteban

3 2

File path encoding
by Sven Van Caekenberghe April 16, 2018

April 16, 2018

Hi, Some people raise issues with file path encoding with non-ASCII characters. The following works fine for me (macOS, Pharo 7, using new File class): "works" (FileLocator temp / 'foo' , 'txt') writeStreamDo: [ :out | out << 'Les Ã©lÃ¨ves FranÃ§ais' ; crlf ]. (FileLocator temp / 'foo' , 'txt') readStreamDo: [ :in | in upToEnd ]. "works" (FileLocator temp / 'benoÃ®t' , 'txt') writeStreamDo: [ :out | out << 'Les Ã©lÃ¨ves FranÃ§ais' ; crlf ]. (FileLocator temp / 'benoÃ®t' , 'txt') readStreamDo: [ :in | in upToEnd ]. "works" (FileLocator temp / 'benoÃ®t') ensureCreateDirectory. (FileLocator temp / 'benoÃ®t' / 'benoÃ®t' , 'txt') writeStreamDo: [ :out | out << 'Les Ã©lÃ¨ves FranÃ§ais' ; crlf ]. (FileLocator temp / 'benoÃ®t' / 'benoÃ®t' , 'txt') readStreamDo: [ :in | in upToEnd ]. Can Linux/Windows users confirm that it works on their platform ? Sven

3 7

Pharo Launcher on Windows > Failing
by phil＠highoctane.be April 16, 2018

April 16, 2018

I wanted to try Pharo Laucher before the tech talk But I get this when asking for an image I do not even know what is going on and I am an "experienced user". The impression this gives to a newcomer is utterly disastrous. We are really on a bad path on this. I'd like to get through this with some Launcher expert and fix this for good. Phil

4 7